Adding warning for missing/blank facility NPI fields (tuva-health#1217)

* Adding warning for facility NPI

* Adding missing eligibility layer docs

---------

Co-authored-by: Andreas Martinson <amartinson193@gmail.com>
Co-authored-by: Aaron Neiderhiser <anneiderhiser@gmail.com>

Author: 3 people

models/input_layer/input_layer__eligibility.yml

@@ -635,6 +635,36 @@ models:
                 tags: ['tuva_dqi_sev_3', 'dqi', 'dqi_cms_hccs']
               arguments:
                 values: ['Continuing', 'New', 'Institutional', 'ESRD', null]
+      - name: hospice_flag
+        description: Whether the patient is in hospice.
+        tests:
+          - the_tuva_project.expect_column_to_exist:
+              config:
+                severity: error
+                enabled: '{{ (var(''enable_input_layer_testing'', true)) | as_bool }}'
+                tags:
+                  - tuva_dqi_sev_1
+                  - dqi    
+      - name: institutional_snp_flag
+        description: Whether the patient is in a special needs plan (SNP) and required to be in nursing home level care. 
+        tests:
+          - the_tuva_project.expect_column_to_exist:
+              config:
+                severity: error
+                enabled: '{{ (var(''enable_input_layer_testing'', true)) | as_bool }}'
+                tags:
+                  - tuva_dqi_sev_1
+                  - dqi    
+      - name: long_term_institutional_flag
+        description: Whether the patient is in an institutional setting for longer than 30 days.
+        tests:
+          - the_tuva_project.expect_column_to_exist:
+              config:
+                severity: error
+                enabled: '{{ (var(''enable_input_layer_testing'', true)) | as_bool }}'
+                tags:
+                  - tuva_dqi_sev_1
+                  - dqi    
       - name: group_id
         description: The group id which multiple members are enrolled for health coverage. This field is a string that can correspond to the particular group under which multiple members are enrolled for health coverage. This could be an identifier that is specific to an employers health plan.
         tests:

models/input_layer/input_layer__medical_claim.yml

@@ -1209,6 +1209,19 @@ models:
       - name: facility_npi
         description: 'Facility NPI for the claim (typically represents the facility where services were performed). This field is a string that contains NPI (National Provider Identifier) values. facility_npi typically represents the location where specific services were delivered. NPIs are composed of numbers and are ten characters in length. DQI ensures that this field matches the expected length and character pattern. Source data may only include a single NPI field without specifying whether the provided identifier corresponds to a rendering, billing, or facility NPI. In that case, look for the NPI in Tuvas provider terminology file to determine whether it corresponds to a person or place. * If its a person, then the NPI should be mapped to rendering_npi. * If its a person and also a professional claim, then also map to billing_npi. * If its a location and the claim type is institutional, then map to facility_npi That logic could look like this: ```sql select ... , case when p.entity_type_code = 1 then npi else null end as rendering_npi , case when p.entity_type_code = 1 and claim_type = professional then p.npi end as billing_npi , case when p.entity_type_code = 2 and claim_type = institutional then p.npi end as facility_npi from source_data as sd left join terminology__provider as p on p.npi = sd.npi ```'
         tests:
+          - not_null:
+              description: >
+                The encounter grouper depends on this field and will not work as intended if this is not provided.
+                If you have an NPI field and are unsure if the NPI is a facility NPI (i.e. level 2 org NPI), then 
+                join to terminology.provider and filter to level 2 NPIs only.
+
+                If left as null, then encounters will under-merge since encounter merging depends on the facility ID field. 
+                There are two primary options if facility NPIs (i.e. level 2 NPIs) are not available:
+                - Leave null: This mean claims will not merge based on encounter grouping logic since all claims are assumed to be in different facilities.
+                - Add a blank string: This will over-merge, but will apply encounter grouping logic and assumes all encounters are at the same facility.
+              config:
+                severity: warn
+                enabled: '{{ (var(''enable_input_layer_testing'', true)) | as_bool }}'        
           - the_tuva_project.expect_column_to_exist:
               config:
                 severity: warn