Definition

The Codeable Concept model provides a unified view of clinical codes and terminology, mapping EMIS codes to SNOMED CT concepts and Read v2 codes where applicable. It enables consistent interpretation and analysis of coded clinical data across different coding systems.

Information

The Codeable Concept model serves as a comprehensive reference for clinical codes used within healthcare systems. It consolidates code information from multiple coding standards, primarily focusing on SNOMED CT mappings for EMIS codes.

Each record in the model represents a unique clinical concept identified by a code_id, linked to its corresponding term and related identifiers in other coding systems. The model facilitates standardized data analysis by providing cross-references between different coding systems that may be used across healthcare applications.

Key features of this model include:

• Mapping between proprietary EMIS codes and standard SNOMED CT concepts
• References to fully specified SNOMED CT names

Changes in iPCV v2

Improved SNOMED CT mapping approach

We have updated how SNOMED CT description IDs are mapped in the Codeable Concept model:

• Changed from using variation_codesnomed in v1 to variation_snomedinteropoutgoing in v2
• Adopted the same approach used in the clinical_code model
• Now using official SNOMED CT mappings rather than legacy mappings

Why?

The previous mapping approach used in v1 was based on legacy mappings created during the Read v2 to SNOMED CT transition in 2020. This provided a granular 1:1 mapping of code IDs to description IDs as found in the EMIS clinical code database, but didn’t align with current SNOMED CT standards

The v2 implementation now uses official SNOMED CT mappings that better represent the intended clinical concepts

Customer benefit

This change provides the following benefits:

• Better alignment with industry-standard SNOMED CT mappings
• Improved consistency between Codeable Concept and Clinical Code models
• Enhanced interoperability with external systems using standard SNOMED CT
• More accurate representation of clinical concepts

Customer action

Customers should review any analyses or queries that rely on SNOMED description IDs, as the values may have changed. If your workflows depend on specific description ID values from v1, you may need to update them to accommodate the new official mappings.

Schema updates for data maintenance

• The is_deleted column has been added to indicate whether a clinical code has been marked as deleted
• The data_filter column is removed as it is no longer required

Benefit

• The is_deleted column enables more effective data maintenance by allowing customers to identify and manage deleted clinical codes
• The data model is streamlined by removing deprecated columns from iPCV v1 and v2, resulting in a cleaner and more efficient structure

Customer Action

• Update your ETL processes to use the is_deleted column to manage and clean up clinical codes
• Review your queries and remove any references to the deprecated data_filter column to align with the updated schema and avoid confusion

Examples

Find SNOMED concepts

SELECT
    term,
    snomed_concept_id,
    fully_specified_name,
    readv2_code
FROM hive.explorer_ipcv.srv_codeable_concept
WHERE term LIKE '%diabetes%'
ORDER BY term
LIMIT 50

Get proprietary EMIS codes

SELECT
    code_id,
    term,
    other_code_system,
    other_code,
    other_display
FROM hive.explorer_ipcv.srv_codeable_concept
WHERE other_code_system IS NOT NULL
LIMIT 100

Map between code systems

-- Query showing the relationship between Read v2 and SNOMED CT codes
SELECT
    readv2_code,
    term,
    snomed_concept_id,
    fully_specified_name
FROM hive.explorer_ipcv.srv_codeable_concept
WHERE
    readv2_code IS NOT NULL
    AND snomed_concept_id IS NOT NULL
ORDER BY readv2_code
LIMIT 100