-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
O2 codes vs concept_ids #226
Comments
In you are in the N3C Enclave you can reference O2 device concept set. |
Hi Stephanie. Is there any data related to ventilator settings (such as SPO2, PaCO2, PaO2, FiO2, air pressure, etc.) in the O2 device concept set? |
@stephanieshong I only see SNOMED codes, not OHDSI concept_ids. |
OHDSI concept_ids are in the O2 device concept set in the Enclave. Hope this helps.
|
Is there any compelling reason why the OMOP concept_ids are kept only in the Enclave and not included as one additional column in the much more assessable spreadsheet linked in the wiki? |
@mgkahn - With your request, we can certainly publish concept set of your interest. We just have not gone around to publishing all of the N3C recommended concept sets from the Enclave to the gitHub. It is my understanding that all of the N3C published papers also publish the concept sets used in the paper. |
@UzmaHasan - You may want to reference following concept set defined in the Enclave. [ICU/MODS]IMV, [ICU/MODS]fio2, [ICU/MODS]pao, ICU, Kostka-ECMO, and [DATOS] Vasopressors (v1). in order to find the ICU cohort. You can use these concept set to look for the concept id in the respective domain to find the cohort. You can also create your own concept set that is a super set of all of these concept set mentioned above. |
@stephanieshong Thank you. I did not know if there were specific policy reasons for keeping the codes in the Enclave rather than on GitHub. There is a higher barrier to accessing the Enclave compared to making the codes available via a link here. I was wondering if N3C had the need for some additional controls, such as logging downloads or tracking provenance, that REQUIRED management within the Enclave. If there is not (as seems to be the case), I would like to propose all codes be moved out of the Enclave and made more accessible here for folks who have not done Enclave training/access. I know that would make life easier for my folks. |
@mgkahn - I am informed that currently, concept sets used in N3C publications are being published here: https://zenodo.org/communities/cd2h-covid/?page=1&size=20 In N3C, we have added extra metadata to go with every concept set we define. (i.e. version number, provenance, limitations and any update information that goes with the concept set versions. ) Currently we do not have a way to download /extract those metadata from the Enclave. I will bring up this issue to the N3C issues meeting. |
@mgkahn - N3C recommended concept sets are listed here: |
The 'Suggested O2 SNOMED Mappings for N3C' table contains the suggested SNOMED codes we should/could use while mapping our oxygen data. Do you also have a spreadsheet with the concept_ids for these? Or do I need to look them up?
The text was updated successfully, but these errors were encountered: