Incremental-Load.md

@@ -20,6 +20,7 @@ The following sections provide an overview of the data flow and processing of re
 ---
 When a Patient resource is read in, the job first checks whether this Patient resource is marked as 'deleted'. If so, this Patient record in OMOP CDM and all other records referenced to this will be delted. If not, the job checks whether this Patient resource already exists in OMOP CDM. This is done in the PERSON table using `fhir_logical_id` or `fhir_identifier`. If the Patient resource already exists in OMOP CDM, an update will take place in OMOP CDM based on the corresponding `person_id`. If the Patient resource does not exist in OMOP CDM, it will be written to OMOP CDM as a new resource.
 
+![inkrementellesLaden-Patient](uploads/c83f19d7791432e95fd4ff4189632e73/inkrementellesLaden-Patient.png)
 
 </details>
 </p>
@@ -34,8 +35,6 @@ When an Encounter resource is read in, the job first checks whether this Encount
 
 Next, the job checks if the Encounter resource already exists in OMOP CDM. This is done in the VISIT_OCCURRENCE table using `fhir_logical_id` or `fhir_identifier`. If the Encounter resource does not exist in OMOP CDM, it will be written to OMOP CDM as a new resource. If the Encounter resource already exists in OMOP CDM, an update will take place in OMOP CDM based on the corresponding `visit_occurrence_id`.
 
-![inkrementellesLaden-Encounter](uploads/a0e34018ceb4052f63f46083578cb006/inkrementellesLaden-Encounter.png)
-
 </details>
 </p>