-
Notifications
You must be signed in to change notification settings - Fork 0
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
Understanding how microbiology laboratory data is stored using the sample data from the Leicester OMOP extract #45
Comments
Explore the different tables from the extract to identify which ones contain the relevant data and matching concept table to tables that contain the relevant microbiology data First look at the following tables to identify microbiology data:
I read in these four tables as data frames into R:
Looking at structure of the Currently filtering information from the OMOP data frames based on concept IDs related to Microbiology - using E.coli as an example to understand how microbiology lab test results are stored across the different OMOP tables |
Installing Ramses using UCLH remote environment
|
Exploring the OMOP extract tables to identify how microbiology lab result data is stored using the web log in version of R-Studio
|
Understanding how the information about identified microorganisms are stored within the OMOP extract tables and how this related to the Ramses Inpatient_microbiology tables In Ramses the microbiology isolate and susceptibility information is stored in three separate data frames:
Ramses has a code to obtain this information and produce these three data frames by using an intermediate a table called inpatient_microbiology. My aim is to re-create this table from the OMOP extract table so it can be input into Ramses using the existing code, the table has the following structure: I want to explore the concept_id table to understand how microbial isolate information is stored.
Just to confirm this I also ran the code:
Mapping the Ramses inpatient_microbiology table to the OMOP extract
As a next step and while I wait for the OMOP extract observation table I will make a synthetic observation table with a few rows of microbiology isolate data and link it to the information in the other OMOP extract tables (Specimen, concept) and try to produce the in_patient_microbiology table to check that the Ramses validate code works with a table other than from the Ramses mock database, I will also look into how the rsi_code and agent_display_name can be obtained form the OMOP extract |
Mapping OMOP to Ramses Inpatient_microbiology table using mock observation table
|
Exploring the new OMOP extract that contains the
|
Linking the This forum discussion is also very helpful and focuses on the The
I now need to match the
I will now pull out the information that is just related to the observation (1147304) and specimen (1147306) tables
From this analysis, the |
To summarise this issue was used to explore how microbiology lab data was stored within the OMOP extract. Here is a summary of what was found:
Mapping the Ramses inpatient_microbiology table to the OMOP extract
|
Here I want to:
concept
table to OMOP tables that contain the relevant microbiology datainpatient_microbiology
table #29The text was updated successfully, but these errors were encountered: