970 | Creating de-duplication logic for patients in both claims and clinical (#971)

* 970 | Creating de-duplication logic for patients in both claims and clinical

Made decision to choose claims over clinical for datasets. Patient table has an expectation of PK on the person_id column.

* Specify only wanting columns from clinical patient

Author: chase-jones

models/core/final/core__patient.sql

@@ -6,9 +6,18 @@
 
 {% if var('clinical_enabled', var('tuva_marts_enabled',False)) == true and var('claims_enabled', var('tuva_marts_enabled',False)) == true -%}
 
-select * from {{ ref('core__stg_claims_patient') }}
+with person_list_to_exclude_because_in_claims as (
+    select distinct person_id
+    from {{ ref('core__stg_claims_patient') }}
+)
+select *
+from {{ ref('core__stg_claims_patient') }}
 union all
-select * from {{ ref('core__stg_clinical_patient') }}
+select cscp.*
+from {{ ref('core__stg_clinical_patient') }} as cscp
+left outer join person_list_to_exclude_because_in_claims as pltebic on cscp.person_id = pltebic.person_id
+/* IF EXISTS IN CLAIMS, CHOOSE CLAIMS RECORD OVER CLINICAL RECORD */
+where pltebic.person_id is null
 
 {% elif var('clinical_enabled', var('tuva_marts_enabled',False)) == true -%}