Add ingest_datetime to core.medical_claim and core.pharmacy_claim (#1263)

Pulls ingest_datetime through from normalized input to core staging and
final models for medical_claim and pharmacy_claim. This field was already
present in core.eligibility. Having both file_date and ingest_datetime in
core strengthens traceability between raw data, input layer, and core,
particularly when a payer sends the same claim across multiple files.

Author: chase-jones

models/core/core_models.yml

@@ -484,6 +484,11 @@ models:
         config:
           meta:
             data_type: timestamp
+      - name: ingest_datetime
+        description: The date and time the source file was ingested into the data warehouse or landed in cloud storage.
+        config:
+          meta:
+            data_type: timestamp
       - name: tuva_last_run
         description: The last time the data was refreshed. Generated by `dbt_utils.pretty_time` as the local time of the `dbt run` environment. Timezone is configurable via the `tuva_last_run` var.
         config:
@@ -1562,6 +1567,11 @@ models:
         config:
           meta:
             data_type: timestamp
+      - name: ingest_datetime
+        description: The date and time the source file was ingested into the data warehouse or landed in cloud storage.
+        config:
+          meta:
+            data_type: timestamp
       - name: tuva_last_run
         description: The last time the data was refreshed. Generated by `dbt_utils.pretty_time` as the local time of the `dbt run` environment. Timezone is configurable via the `tuva_last_run` var.
         config:
@@ -2303,6 +2313,11 @@ models:
         config:
           meta:
             data_type: timestamp
+      - name: ingest_datetime
+        description: The date and time the source file was ingested into the data warehouse or landed in cloud storage.
+        config:
+          meta:
+            data_type: timestamp
       - name: tuva_last_run
         description: The last time the data was refreshed. Generated by `dbt_utils.pretty_time` as the local time of the `dbt run` environment. Timezone is configurable via the `tuva_last_run` var.
         config:

models/core/final/core__medical_claim.sql

@@ -75,6 +75,7 @@
 {%- set tuva_metadata_columns -%}
     , data_source
     , file_date
+    , ingest_datetime
     , file_name
     , tuva_last_run
 {%- endset %}

models/core/final/core__pharmacy_claim.sql

@@ -41,6 +41,7 @@
 {%- set tuva_metadata_columns -%}
     , data_source
     , file_date
+    , ingest_datetime
     , file_name
     , tuva_last_run
 {%- endset %}

models/core/staging/core__stg_claims_medical_claim.sql

@@ -89,6 +89,7 @@
 {%- set tuva_metadata_columns -%}
        , cast(med.data_source as {{ dbt.type_string() }}) as data_source
     , cast(med.file_date as {{ dbt.type_timestamp() }}) as file_date
+    , cast(med.ingest_datetime as {{ dbt.type_timestamp() }}) as ingest_datetime
     , cast(med.file_name as {{ dbt.type_string() }}) as file_name
     , cast('{{ var('tuva_last_run') }}' as {{ dbt.type_timestamp() }}) as tuva_last_run
 {%- endset %}

models/core/staging/core__stg_claims_pharmacy_claim.sql

@@ -51,6 +51,7 @@
 {%- set tuva_metadata_columns -%}
        , cast(pharm.data_source as {{ dbt.type_string() }}) as data_source
        , cast(pharm.file_date as {{ dbt.type_timestamp() }}) as file_date
+       , cast(pharm.ingest_datetime as {{ dbt.type_timestamp() }}) as ingest_datetime
        , cast(pharm.file_name as {{ dbt.type_string() }}) as file_name
        , cast('{{ var('tuva_last_run') }}' as {{ dbt.type_timestamp() }}) as tuva_last_run
 {%- endset %}