SNOMED CT Concept Hierarchies for Computable Clinical Phenotypes From Electronic Health Record Data: Comparison of Intensional Versus Extensional Value Sets

Abstract

BackgroundDefining clinical phenotypes from electronic health record (EHR)–derived data proves crucial for clinical decision support, population health endeavors, and translational research. EHR diagnoses now commonly draw from a finely grained clinical terminology—either native SNOMED CT or a vendor-supplied terminology mapped to SNOMED CT concepts as the standard for EHR interoperability. Accordingly, electronic clinical quality measures (eCQMs) increasingly define clinical phenotypes with SNOMED CT value sets. The work of creating and maintaining list-based value sets proves daunting, as does insuring that their contents accurately represent the clinically intended condition.ObjectiveThe goal of the research was to compare an intensional (concept hierarchy-based) versus extensional (list-based) value set approach to defining clinical phenotypes using SNOMED CT–encoded data from EHRs by evaluating value set conciseness, time to create, and completeness.MethodsStarting from published Centers for Medicare and Medicaid Services (CMS) high-priority eCQMs, we selected 10 clinical conditions referenced by those eCQMs. For each, the published SNOMED CT list-based (extensional) value set was downloaded from the Value Set Authority Center (VSAC). Ten corresponding SNOMED CT hierarchy-based intensional value sets for the same conditions were identified within our EHR. From each hierarchy-based intensional value set, an exactly equivalent full extensional value set was derived enumerating all included descendant SNOMED CT concepts. Comparisons were then made between (1) VSAC-downloaded list-based (extensional) value sets, (2) corresponding hierarchy-based intensional value sets for the same conditions, and (3) derived list-based (extensional) value sets exactly equivalent to the hierarchy-based intensional value sets. Value set conciseness was assessed by the number of SNOMED CT concepts needed for definition. Time to construct the value sets for local use was measured. Value set completeness was assessed by comparing contents of the downloaded extensional versus intensional value sets. Two measures of content completeness were made: for individual SNOMED CT concepts and for the mapped diagnosis clinical terms available for selection within the EHR by clinicians.ResultsThe 10 hierarchy-based intensional value sets proved far simpler and faster to construct than exactly equivalent derived extensional value set lists, requiring a median 3 versus 78 concepts to define and 5 versus 37 minutes to build. The hierarchy-based intensional value sets also proved more complete: in comparison, the 10 downloaded 2018 extensional value sets contained a median of just 35% of the intensional value sets’ SNOMED CT concepts and 65% of mapped EHR clinical terms.ConclusionsIn the EHR era, defining conditions preferentially should employ SNOMED CT concept hierarchy-based (intensional) value sets rather than extensional lists. By doing so, clinical guideline and eCQM authors can more readily engage specialists in vetting condition subtypes to i...

Recommendation mapping of the World Health Organization's guidelines on tuberculosis: A new approach to digitizing and presenting recommendations

“…Please cite this article as: A. Hajizadeh et al, Recommendation mapping of the World Health Organization's guidelines on tuberculosis: A new approach to digitizing and presenting recommendations, Journal of Clinical Epidemiology, https:// doi.org/ 10.1016/ j.jclinepi.2021.02.009ARTICLE IN PRESSJID: JCE [mNS;April 2, 2021;16:7 ] …”

Electronic Health Records–Based Cardio-Oncology Registry for Care Gap Identification and Pragmatic Research: Procedure and Observational Study

“…EHR-based registries for specialized conditions can be constructed in short time frames (weeks to months) using replicable frameworks [ 4 ] and can then be employed for investigation. For multisite, multi-EHR studies, mapping of EHR fields to standard terminologies (SNOMED, LOINC, RxNorm) now required for EHR certification on interoperability can be leveraged for defining conditions [ 5 ], observations, and medications identically across all sites. Multicenter studies are expedited by adoption of a common data model.…”

“…Electronic health records (EHRs) used for day-to-day patient care activities provide a unique repository of aggregate data about this at-risk population [ 4 ]. Hierarchical EHR databases harbor rich clinical data with specificity exceeding the information available from flat file claims data because EHR diagnoses are encoded with SNOMED CT (formerly Systematized Nomenclature of Medicine-Clinical Terms) instead of claims data that are encoded solely based on International Classification of Diseases, Tenth Revision (ICD-10) codes [ 5 ]. For instance, renal cell carcinoma, nephroblastoma, renal sarcoma, and multiple other kidney cancer types all share a single ICD-10 code and cannot be differentiated by ICD-10–encoded claims data, necessitating manual chart review for differentiation.…”

Representing glycophenotypes: semantic unification of glycobiology resources for disease discovery

“…The Monarch platform uses the Mondo Disease Ontology that provides a harmonized and computable foundation for associating phenotypes to diseases (21, 22). Mondo integrates the existing sources of disease definitions, including the Disease Ontology (23), the National Cancer Institute Thesaurus (NCIt) (24), the Online Mendelian Inheritance in Man (OMIM) (25), Systematized Nomenclature of Medicine–Clinical Terms (SNOMED CT) (26), International Classification of Diseases (27), International Classification of Diseases for Oncology (28), OncoTree (29), MedGen (30) and numerous others into a single, coherent merged ontology. Mondo is co-developed with the HPO, to ensure comprehensive representation of diseases and phenotypes.…”