-
When compared to OMOP2OBO, SSSOM lacks expressivity at first glance. Here is an example:
```
Example: Hip pain (OMOP_4170554)
Ontology Concepts:
Hip pain (HP_0030838)
Arthralgia of the hip (HP…
-
Hi, I just noticed that diagnosis was was not extracted and transformed to CONDITION_OCCURRENCE table. Since diagnosis are very important in many pipelines, do you have plans to also support this?
…
-
The Clinical Trials Working Group proposes conventions for the OMOP CDM and Standardized Vocabularies **to capture clinical trial specific data**.
Our **use case** is the conversion of clinical tri…
-
The guidance indicates the following recommended database and schema set up:
"export OMOP_SCHEMA='omop'
export OMOP='host=localhost dbname=postgres user=postgres options=--search_path='$OMOP_SCHEMA
…
-
## Overview
We want mapping content from various sources to be converted into SSSOM TSV, and then converted into FHIR ConceptMap JSON, and uploaded to the TIMS server.
## Data sources
- [ ] 1. FH…
-
Original code sets two fields hard coded to zero. Is this correct?
,0 AS OBSERVATION_SOURCE_CONCEPT_ID
,0 AS UNIT_SOURCE_VALUE
OMOP best practices asks for zeroes under circunstances, b…
-
So from what I understand, you will have to provide FHIR ConceptMap(s) to define mapping for the codes from your FHIR resources, such as persons, encounters, conditions, diagnosis, etc to OMOP concept…
-
https://github.com/amazon-science/nl2sql-omop-cdm/blob/main/nonzero_args_by_query.json
Missing.
-
So from what I understand, you will have to provide FHIR Concept Map(s) to define mapping for the codes from your FHIR resources, such as persons, encounters, conditions, diagnosis, etc to OMOP concep…
-
The following non-standard codes are contained in the N3C phenotype script
756023 - dx_strong
756044 - dx_strong
756061 - dx_strong
756081 - dx_strong
37310285 - dx_strong
Luckily the standa…