Update Incremental Load authored by Henke, Elisa's avatar Henke, Elisa
...@@ -69,13 +69,11 @@ Due to the fact that the resource types are read in random order, it may happen ...@@ -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: 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** | Resource type | Table | Column |
* table: VISIT_DETAIL | :------: | :------: | :------ |
* columns: person_id, procedure_concept_id, procedure_datetime, procedure_source_concept_id | 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 |
**Procedure resource** | Observation | observation <br> measurement |
* table: PROCEDURE_OCCURRENCE
* columns: person_id, visit_detail_start_datetime, visit_occurrence_id
![inkrementellesLaden-Others](uploads/9c72e7aa867269a57cce9e9bc74495de/inkrementellesLaden-Others.png) ![inkrementellesLaden-Others](uploads/9c72e7aa867269a57cce9e9bc74495de/inkrementellesLaden-Others.png)
... ...
......