You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, ETL generates a table for each encounter type and has the cancel_date_time column as well, but when an encounter is cancelled, ETL updates that entry in the encounter's cancel table separately. But ideally it should have been done in any of the following ways, in order to avoid confusions to the developers -
Either the cancel_date_time and the last_modified details should get updated in the encounter table as well
Or the cancel_date_time column shouldn't be part of the encounter table in ETL.
On of the above options should be considered and implemented so that devs have clear approach when handling cancel scenarios in the reports logic.
The text was updated successfully, but these errors were encountered:
Currently, ETL generates a table for each encounter type and has the cancel_date_time column as well, but when an encounter is cancelled, ETL updates that entry in the encounter's cancel table separately. But ideally it should have been done in any of the following ways, in order to avoid confusions to the developers -
On of the above options should be considered and implemented so that devs have clear approach when handling cancel scenarios in the reports logic.
The text was updated successfully, but these errors were encountered: