... | ... | @@ -11,7 +11,7 @@ When the job runs as incremental load, all resources are processed in a random o |
|
|
<details>
|
|
|
<summary> Show data flow of Patient resources </summary>
|
|
|
|
|
|
When a patient resource is read in, the job first checks whether this patient resource already exists in OMOP CDM. This is done in the FHIR_ID_TO_OMOP_ID_MAP table using the logical_id and/or the identifier. If the patient resource does not yet exist in OMOP CDM, it will be written to OMOP CDM as a new resource. If the patient resource already exists in OMOP CDM, an update will take place in OMOP CDM based on the corresponding person_id (= omop_id from FHIR_ID_TO_OMOP_ID_MAP).
|
|
|
When a Patient resource is read in, the job first checks whether this Patient resource already exists in OMOP CDM. This is done in the FHIR_ID_TO_OMOP_ID_MAP table using the logical_id and/or the identifier. If the Patient resource already exists in OMOP CDM, an update will take place in OMOP CDM based on the corresponding person_id (= omop_id from FHIR_ID_TO_OMOP_ID_MAP). If the Patient resource does not yet exist in OMOP CDM, it will be written to OMOP CDM as a new resource.
|
|
|
|
|
|

|
|
|
|
... | ... | |