| ... | ... | @@ -69,13 +69,11 @@ Due to the fact that the resource types are read in random order, it may happen |
|
|
|
|
|
|
|
Next the job checks if the read resource (e.g. Condition) already exists in OMOP CDM. This is done in the following tables using specific columns:
|
|
|
|
|
|
|
|
**Encounter resource**
|
|
|
|
* table: VISIT_DETAIL
|
|
|
|
* columns: person_id, procedure_concept_id, procedure_datetime, procedure_source_concept_id
|
|
|
|
|
|
|
|
**Procedure resource**
|
|
|
|
* table: PROCEDURE_OCCURRENCE
|
|
|
|
* columns: person_id, visit_detail_start_datetime, visit_occurrence_id
|
|
|
|
| Resource type | Table | Column |
|
|
|
|
| :------: | :------: | :------ |
|
|
|
|
| Encounter | VISIT_DETAIL | person_id <br> visit_detail_start_datetime <br> visit_occurrence_id |
|
|
|
|
| Procedure | PROCEDURE_OCCURRENCE | person_id <br> procedure_concept_id <br> procedure_datetime <br> procedure_source_concept_id |
|
|
|
|
| Observation | observation <br> measurement |
|
|
|
|
|
|
|
|
|
|
|
|
|
| ... | ... | |
