Describe the bug - Required
In instance where different encounter ID dates overlap, the entire encounter get's thrown out for readmissions calculations. I think it makes more sense to at least let the most informational encounter through into the readmission logic, versus throwing out all associated encounters.
Environment - Required
- Tuva project package version (e.g. 0.6.0): 0.14.15
- dbt version (e.g. 1.7): 1.9.X
- dbt type (e.g. dbt cloud or dbt CLI): dbt core
- Data warehouse (e.g. Snowflake): dbt cloud
Describe the bug - Required
In instance where different encounter ID dates overlap, the entire encounter get's thrown out for readmissions calculations. I think it makes more sense to at least let the most informational encounter through into the readmission logic, versus throwing out all associated encounters.
Environment - Required