| ... | ... | @@ -41,6 +41,12 @@ Next, the job checks if the Encounter resource already exists in OMOP CDM. This |
|
|
|
<details>
|
|
|
|
<summary> Show data flow of Medication and MedicationAdministration resources </summary>
|
|
|
|
|
|
|
|
### Medication
|
|
|
|
|
|
|
|
When a Medication resource is read in, the job first checks whether this Medication 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 Medication resource does not yet exist in OMOP CDM, it will be written to OMOP CDM as a new resource. If the Medication resource already exists in OMOP CDM, an update will take place in FHIR_ID_TO_OMOP_ID_MAP.
|
|
|
|
|
|
|
|
### MedicationAdministration
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</details>
|
| ... | ... | |
