Skip to content

Changes

Page history
Added logic for Immunization, DiagnosticReport and Consent resources authored by Henke, Elisa's avatar Henke, Elisa
Hide whitespace changes
Inline Side-by-side
Incremental-Load.md
View page @ 7dd98152
......@@ -62,17 +62,17 @@ Next, it checks whether the referenced Medication resource already exists in OMO
</details>
</p>
## Department Case, Procedure, Observation, MedicationAdministration, MedicationStatement, Condition
## Department Case, Procedure, Observation, MedicationAdministration, MedicationStatement, Condition, Immunization, DiagnosticReport, Consent
<p>
<details>
<summary> Show data flow of Encounter, Procedure, Observation, MedicationAdministration, MedicationStatement and Condition resources </summary>
<summary> Show data flow of Encounter, Procedure, Observation, MedicationAdministration, MedicationStatement, Condition, Immunization, DiagnosticReport and Consent resources </summary>
---
When an Encounter/Procedure/Observation/MedicationAdministration/MedicationStatement/Condition resource is read in, the job first tries to delete possible already existing records in OMOP CDM using `fhir_logical_id` or `fhir_identifier`. If the resource is marked as 'deleted', no further transfomation will be occured. Otherwise the read resource is processed as a new resource (analog bulk load).
When an Encounter/Procedure/Observation/MedicationAdministration/MedicationStatement/Condition/Immunization/DiagnosticReport/Consent resource is read in, the job first tries to delete possible already existing records in OMOP CDM using `fhir_logical_id` or `fhir_identifier`. If the resource is marked as 'deleted', no further transformation will be occurred. Otherwise, the read resource is processed as a new resource (analog bulk load).
The job checks whether the referenced Patient resource already exists in OMOP CDM. This is done in PERSON and table using `fhir_logical_id` or `fhir_identifier`. If the referenced Patient resource is not available in OMOP CDM, the read Encounter/Procedure/Observation/MedicationAdministration/MedicationStatement/Condition resource is skipped. If the referenced Patient resource already exists in OMOP CDM, the existing `person_id` will be used. After this step, the further processing of the read resource is done analog to bulk load.
The job checks whether the referenced Patient resource already exists in OMOP CDM. This is done in PERSON table using `fhir_logical_id` or `fhir_identifier`. If the referenced Patient resource is not available in OMOP CDM, the read Encounter/Procedure/Observation/MedicationAdministration/MedicationStatement/Condition/Immunization/DiagnosticReport/Consent resource is skipped. If the referenced Patient resource already exists in OMOP CDM, the existing `person_id` will be used. After this step, the further processing of the read resource is done analog to bulk load.
![inkrementellesLaden-Others](uploads/5d43c97e8c0c8606c0ca32573de21b61/inkrementellesLaden-Others.png)
![inkrementellesLaden-Others](uploads/d810148f31bbde4991270d06415687c6/inkrementellesLaden-Others.png)
</details>
</p>
\ No newline at end of file