-
@stephanieshong wrote some helpful text for new RWD blurbs that may be better rolled into the main text of ch 3 as it is OMOP-focused:
"Harmonized EHR data is organized by key domains such as condi…
-
-
During an exercise in the CDM WG, we discovered a remnant of an OMOP CDM v6 table in the Atlas Cohort Definition interface. This results in a cohort definition that will not run on OMOP CDM v5.4.
W…
-
Hey, thanks for the great product. Just wondering whether this can provide support for SQL server. We already have a OMOP CMD instance based on SQL server. We would like to build a FHIR server on top …
-
We will need to merge data from the EHR with data from other sources (machines, images etc).
We will need to do that merge before we anonymise and export.
Tim Roberts has a method already in place for…
-
ICD10CM concepts Z19.1|Hormone sensitive malignancy status, Z19.2|Hormone resistant malignancy status
don't have a proper target concept in OMOP, they are just maped 1340204|History of event + 443392…
-
I've been able to follow the tutorial in the README just fine, except for the last line.
I've downloaded the Synthea data, converted it to the training data format, and used this line to create a pr…
-
When running the default dbt build for omop (step 11 of README) it throw an error:
as below:
02:41:42 Finished running 85 table models, 28 seeds, 425 data tests in 0 hours 0 minutes and 34.85 s…
-
-
Due to some of the OMOP clinical vocabularies having licensing restrictions, we need to decide how and in what format the mappings will be publicly released.
Regardless of the above issue, we wil…