DOI: 10.5281/zenodo.7249166
title: N3C-Formatted OMOP2OBO Mappings

description: <strong>OMOP2OBO Mappings - N3C OMOP to OBO Working group</strong> This repository stores OMOP2OBO mappings which have been processed for use within the National COVID Cohort Collaborative (N3C) Enclave. The version of the mappings stored in this repository have been specifically formatted for use within the N3C Enclave. <strong>N3C OMOP to OBO Working Group: </strong>https://covid.cd2h.org/ontology <em><strong>Accessing the N3C-Formatted Mappings </strong></em> You can access the three OMOP2OBO HPO mapping files in the Enclave from the Knowledge store using the following link: https://unite.nih.gov/workspace/compass/view/ri.compass.main.folder.1719efcf-9a87-484f-9a67-be6a29598567. The mapping set includes three files, but you only need to merge the following two files with existing data in the Enclave in order to be able to create the concept sets: <em>OMOP2OBO_v1.0.0_N3C_Enclave_CSV_concept_set_expression_items.csv</em> <em>OMOP2OBO_v1.0.0_N3C_Enclave_CSV_concept_set_version.csv</em> The first file <em>OMOP2OBO_v1.0.0_N3C_Enclave_CSV_concept_set_expression_items.csv</em>, contains columns for the OMOP concept ids and codes as well as specifies information like whether or not the OMOP concept’s descendants should be included when deriving the concept sets (defaults to FALSE). The other file <em>OMOP2OBO_v1.0.0_N3C_Enclave_CSV_concept_set_version.csv</em>, contains details on the mapping’s label (i.e., the HPO curie and label in the concept_set_id field) and its provenance/evidence (the specific column to access for this information is called intention). <em><strong>Creating Concept Sets</strong></em> Merge these files together on the column named <em>codeset_id</em> and then join them with existing Enclave tables like concept and <em>condition_occurrence</em> to populate the actual concept sets. The name of the concept set can be obtained from the <em>OMOP2OBO_v1.0.0_N3C_Enclave_CSV_concept_set_version.csv</em> file and is stored as a string in the column called <em>concept_set_id</em>. Although not ideal (but is the best way to approach this currently given what fields are available in the Enclave), to get the HPO CURIE and label will require applying a regex to this column. An example mapping is shown below (highlighting some of the most useful columns): <pre><code>codeset_id: 900000000 concept_set_id: [OMOP2OBO] hp_0002031-abnormal_esophagus_morphology concept: 23868 code: 69771008 codeSystem: SNOMED includeDescendants: False intention: Mixed - This mapping was created using the OMOP2OBO mapping algorithm (https://github.com/callahantiff/OMOP2OBO). The Mapping Category and Evidence supporting the mappings are provided below, by OMOP concept: 23868 ******* Mapping Category: Automatic Exact - Concept ------------------------------------------------ Mapping Provenance ------------------ OBO_DbXref-OMOP_ANCESTOR_SOURCE_CODE:snomed_69771008 | OBO_DbXref-OMOP_CONCEPT_SOURCE_CODE:snomed_69771008 | CONCEPT_SIMILARITY:HP_0002031_0.713</code></pre> <strong>Release Notes - v1.0.0</strong> <em>Preparation</em> In order to import data into the Enclave, the following items are needed: Obtain API Token, which will be included in the authorization header (stored as GitHub Secret) Obtain username hash from the Enclave OMOP2OBO Mappings (v1.0.0) <em>Data</em> Concept Set Container (<em>concept_set_container</em>): <em>CreateNewConceptSet</em> Concept Set Version (<em>code_sets</em>): C<em>reateNewDraftOMOPConceptSetVersion</em> Concept Set Expression Items (<em>concept_set_version_item</em>): <em>addCodeAsVersionExpression</em> <em>Script</em> <em>n3c_mapping_conversion.py</em>: https://github.com/callahantiff/OMOP2OBO/tree/master/applications/N3C <em>Generated Output</em> Need to have the <em>codeset_id</em> filled from self-generation (ideally, from a conserved range) prior to beginning any of the API steps. The current list of assigned identifiers is stored in the file named <em>omop2obo_enclave_codeset_id_dict_v1.0.0.json</em>. To be consistent with OMOP tools, specifically Atlas, we have also created Atlas-formatted json files for each mapping, which are stored in the zipped directory named <em>atlas_json_files_v1.0.0.zip</em>. <strong>File 1: concept_set_container</strong> <strong>Generated Data:</strong> <em>OMOP2OBO_v1.0.0_N3C_Enclave_CSV_concept_set_container.csv</em> Columns: concept_set_id concept_set_name intention assigned_informatician assigned_sme project_id status stage n3c_reviewer alias archived created_by created_at <strong>File 2: concept_set_expression_items</strong> <strong>Generated Data: </strong><em>OMOP2OBO_v1.0.0_N3C_Enclave_CSV_concept_set_expression_items.csv</em> Columns: codeset_id concept_id code codeSystem isExcluded includeDescendants includeMapped item_id annotation created_by created_at <strong>File 3: concept_set_version</strong> <strong>Generated Data: </strong><em>OMOP2OBO_v1.0.0_N3C_Enclave_CSV_concept_set_version.csv</em> Columns: codeset_id concept_set_id concept_set_version_title project source_application source_application_version created_at atlas_json most_recent_version comments intention limitations issues update_message status has_review reviewed_by created_by provenance atlas_json_resource_url parent_version_id is_draft <strong><em>Generated Output:</em></strong> OMOP2OBO_v1.0.0_N3C_Enclave_CSV_concept_set_container.csv OMOP2OBO_v1.0.0_N3C_Enclave_CSV_concept_set_expression_items.csv OMOP2OBO_v1.0.0_N3C_Enclave_CSV_concept_set_version.csv atlas_json_files_v1.0.0.zip omop2obo_enclave_codeset_id_dict_v1.0.0.json
description: These concepts are processed from the original OMOP2OBO condition occurrence mappings, available here: https://doi.org/10.5281/zenodo.6774363