Data Quality Test Catalog

This catalog is generated directly from the explicit Logical Data Quality test registry in the Tuva Core version used to build this documentation. Compare the published source provenance with your installed version when investigating a different release. It is the complete list of built-in Logical Data Quality tests for that version. Tuva does not infer the display name, description, Test Type, Severity, or affected Input Layer fields from the test name.

Each entry identifies the Input Layer Model the test evaluates and includes the test's stable name, description, affected Input Layer fields, Test Type, and Severity. The public data_quality.logical_test_catalog and data_quality.logical_test_input_columns relations provide the enabled warehouse representation of this metadata.

An affected Input Layer field is a field whose value a test failure calls into question and that a user may need to correct. A field used only to determine whether the test applies is not an affected field.

Test Type describes the kind of data issue the test evaluates. Severity describes the expected impact of a failure on Tuva's ability to run correctly or produce trustworthy analytics. See How to Use Logical Data Quality for the definitions of each Test Type and Severity.

Use the table filter or search box to find tests for a specific Input Layer Model, field, or Data Quality issue.

Each of the 72 Input Layer DATE and timestamp fields has exactly one S2 Logical invalid range check. Bounds vary by meaning: historical clinical and person dates can begin in 1900, transactional and ingestion dates begin in 2000, and appointments, enrollment start dates, and finite enrollment end dates can extend 12 months beyond the current date. The accepted eligibility.enrollment_end_date = 9999-12-31 open-span alias is not applicable and is canonicalized to null downstream. Structural Data Quality, not this catalog, validates compatible native types; YYYY-MM-DD is the required representation when a connector parses or serializes a date as text. See the complete range matrix.

Input Layer ModelAll Input Layer Modelsappointmentconditioneligibilityencounterimmunizationlab_resultlocationmedical_claimmedicationobservationpatientpharmacy_claimpractitionerprocedureprovider_attribution

Search

314 tests

Input Layer Model

Test Name

Test Description

Affected Input Layer Fields

Test Type

Severity

appointment

duration is negativeappointment__duration_negative

Checks whether a populated appointment duration is negative.

duration

invalid

Severity 2

appointment

encounter_id not found in encounter tableappointment__encounter_id_not_in_encounter

Checks whether populated encounter_id values in the appointment Input Layer Model have a corresponding encounter_id in the encounter Input Layer Model for the same data_source.

encounter_id, data_source

referential

Severity 2

appointment

encounter_id, person_id, and patient_id combination not found in encounter tableappointment__encounter_person_patient_pair_not_in_encounter

Checks whether a populated encounter_id exists for the data_source and the populated person_id and patient_id pair exists in the patient Input Layer Model, but the encounter is not assigned to that exact pair in the encounter Input Layer Model.

encounter_id, person_id, patient_id, data_source

referential

Severity 2

appointment

end datetime before start datetimeappointment__end_datetime_before_start_datetime

Checks whether a populated appointment end_datetime occurs before start_datetime.

start_datetime, end_datetime

temporal

Severity 2

appointment

end_datetime is out of reasonable rangeappointment__end_datetime_out_of_reasonable_range

Checks whether a populated appointment end_datetime is before 2000-01-01 or after the date 12 months after the current date.

end_datetime

invalid

Severity 2

appointment

ingest_datetime is out of reasonable rangeappointment__ingest_datetime_out_of_reasonable_range

Checks whether a populated ingest_datetime in the appointment Input Layer Model is before 2000-01-01 or after the current date.

ingest_datetime

invalid

Severity 2

appointment

patient_id not found in patient tableappointment__patient_id_not_in_patient

Checks whether patient_id values in the appointment Input Layer Model have a corresponding patient_id in the patient Input Layer Model for the same data_source.

patient_id, data_source

referential

Severity 2

appointment

person_id and patient_id pair not found in patient tableappointment__person_patient_pair_not_in_patient

Checks whether populated person_id and patient_id values each exist in the patient Input Layer Model for the same data_source but their exact pair does not.

person_id, patient_id, data_source

referential

Severity 2

appointment

person_id not found in patient tableappointment__person_id_not_in_patient

Checks whether person_id values in the appointment Input Layer Model have a corresponding person_id in the patient Input Layer Model for the same data_source.

person_id, data_source

referential

Severity 2

appointment

start_datetime is nullappointment__start_datetime_null

Checks whether start_datetime is null in the appointment Input Layer Model.

start_datetime

missing

Severity 2

appointment

start_datetime is out of reasonable rangeappointment__start_datetime_out_of_reasonable_range

Checks whether a populated appointment start_datetime is before 2000-01-01 or after the date 12 months after the current date.

start_datetime

invalid

Severity 2

condition

code_system is invalidcondition__code_system_invalid

Checks whether code_system in the condition Input Layer Model is populated with a value other than the exact lowercase values icd-9-cm, icd-10-cm, snomed-ct, or unknown.

code_system

invalid

Severity 2

condition

code_system is nullcondition__code_system_null

Checks whether code_system is null in the condition Input Layer Model.

code_system

missing

Severity 2

condition

condition rank is not positivecondition__condition_rank_not_positive

Checks whether a populated condition_rank in the condition Input Layer Model is zero or negative.

condition_rank

invalid

Severity 2

condition

encounter_id not found in encounter tablecondition__encounter_id_not_in_encounter

Checks whether populated encounter_id values in the condition Input Layer Model have a corresponding encounter_id in the encounter Input Layer Model for the same data_source.

encounter_id, data_source

referential

Severity 2

condition

encounter_id, person_id, and patient_id combination not found in encounter tablecondition__encounter_person_patient_pair_not_in_encounter

Checks whether a populated encounter_id exists for the data_source and the populated person_id and patient_id pair exists in the patient Input Layer Model, but the encounter is not assigned to that exact pair in the encounter Input Layer Model.

encounter_id, person_id, patient_id, data_source

referential

Severity 2

condition

ingest_datetime is out of reasonable rangecondition__ingest_datetime_out_of_reasonable_range

Checks whether a populated ingest_datetime in the condition Input Layer Model is before 2000-01-01 or after the current date.

ingest_datetime

invalid

Severity 2

condition

onset date is after resolved datecondition__onset_date_after_resolved_date

Checks whether a populated condition onset_date occurs after resolved_date.

onset_date, resolved_date

temporal

Severity 2

condition

onset date is out of reasonable rangecondition__onset_date_out_of_reasonable_range

Checks whether a populated condition onset_date is before 1900-01-01 or after the current date.

onset_date

invalid

Severity 2

condition

patient_id is nullcondition__patient_id_null

Checks whether patient_id is null in the condition Input Layer Model.

patient_id

missing

Severity 2

condition

patient_id not found in patient tablecondition__patient_id_not_in_patient

Checks whether patient_id values in the condition Input Layer Model have a corresponding patient_id in the patient Input Layer Model for the same data_source.

patient_id, data_source

referential

Severity 2

condition

person_id and patient_id pair not found in patient tablecondition__person_patient_pair_not_in_patient

Checks whether populated person_id and patient_id values each exist in the patient Input Layer Model for the same data_source but their exact pair does not.

person_id, patient_id, data_source

referential

Severity 2

condition

person_id is nullcondition__person_id_null

Checks whether person_id is null in the condition Input Layer Model.

person_id

missing

Severity 2

condition

person_id not found in patient tablecondition__person_id_not_in_patient

Checks whether person_id values in the condition Input Layer Model have a corresponding person_id in the patient Input Layer Model for the same data_source.

person_id, data_source

referential

Severity 2

condition

present_on_admit_code is invalidcondition__present_on_admit_code_invalid

Checks whether present_on_admit_code is populated but not found in Tuva present on admission terminology.

present_on_admit_code

invalid

Severity 2

condition

recorded date is out of reasonable rangecondition__recorded_date_out_of_reasonable_range

Checks whether a populated condition recorded_date is before 1900-01-01 or after the current date.

recorded_date

invalid

Severity 2

condition

resolved date is out of reasonable rangecondition__resolved_date_out_of_reasonable_range

Checks whether a populated condition resolved_date is before 1900-01-01 or after the current date.

resolved_date

invalid

Severity 2

condition

source_code is invalidcondition__source_code_invalid

Checks whether source_code in the condition Input Layer Model is populated and code_system is one of the exact lowercase supported standard values, but source_code is not found in the corresponding terminology table.

code_system, source_code

invalid

Severity 2

condition

source_code is nullcondition__source_code_null

Checks whether source_code is null in the condition Input Layer Model.

source_code

missing

Severity 2

eligibility

birth_date has multiple values per person_ideligibility__multiple_birth_dates_per_person

Checks whether the same person_id and data_source identify records with more than one non-null birth_date in the eligibility Input Layer Model.

birth_date

consistency

Severity 2

eligibility

birth_date is after death_dateeligibility__birth_date_after_death_date

Checks whether birth_date is after death_date in the eligibility Input Layer Model.

birth_date, death_date

temporal

Severity 2

eligibility

birth_date is nulleligibility__birth_date_null

Checks whether birth_date is null in the eligibility Input Layer Model.

birth_date

missing

Severity 2

eligibility

birth_date is out of reasonable rangeeligibility__birth_date_out_of_reasonable_range

Checks whether birth_date in the eligibility Input Layer Model is before 1900-01-01 or after the current date.

birth_date

invalid

Severity 2

eligibility

death_date is out of reasonable rangeeligibility__death_date_out_of_reasonable_range

Checks whether death_date in the eligibility Input Layer Model is before 1900-01-01 or after the current date.

death_date

invalid

Severity 2

eligibility

death_flag indicates death without death_dateeligibility__death_flag_without_death_date

Checks whether death_flag is 1 in the eligibility Input Layer Model while death_date is null.

death_date, death_flag

consistency

Severity 3

eligibility

death_flag is invalideligibility__death_flag_invalid

Checks whether death_flag in the eligibility Input Layer Model is populated with a value other than 0 or 1.

death_flag

invalid

Severity 3

eligibility

enrollment_end_date is outside the supported date rangeeligibility__enrollment_end_date_outside_supported_date_range

Checks whether a populated finite enrollment_end_date in the eligibility Input Layer Model is before 1900-01-01 or after the date 12 months after the current date. Null and the accepted 9999-12-31 open-span alias are not applicable. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

enrollment_end_date

invalid

Severity 2

eligibility

enrollment_start_date is after enrollment_end_dateeligibility__enrollment_start_after_end

Checks whether enrollment_start_date is after a populated finite enrollment_end_date in the eligibility Input Layer Model. Null and the legacy 9999-12-31 alias represent an open span and are not applicable.

enrollment_start_date, enrollment_end_date

temporal

Severity 1

eligibility

enrollment_start_date is outside the supported date rangeeligibility__enrollment_start_date_outside_supported_date_range

Checks whether a populated enrollment_start_date in the eligibility Input Layer Model is before 1900-01-01 or after the date 12 months after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

enrollment_start_date

invalid

Severity 2

eligibility

file_date is outside the supported date rangeeligibility__file_date_outside_supported_date_range

Checks whether a populated file_date in the eligibility Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

file_date

invalid

Severity 2

eligibility

hospice_flag is invalideligibility__hospice_flag_invalid

Checks whether hospice_flag in the eligibility Input Layer Model is populated with a value other than 0 or 1.

hospice_flag

invalid

Severity 2

eligibility

ingest_datetime is out of reasonable rangeeligibility__ingest_datetime_out_of_reasonable_range

Checks whether a populated ingest_datetime in the eligibility Input Layer Model is before 2000-01-01 or after the current date.

ingest_datetime

invalid

Severity 2

eligibility

institutional_snp_flag is invalideligibility__institutional_snp_flag_invalid

Checks whether institutional_snp_flag in the eligibility Input Layer Model is populated with a value other than 0 or 1.

institutional_snp_flag

invalid

Severity 2

eligibility

long_term_institutional_flag is invalideligibility__long_term_institutional_flag_invalid

Checks whether long_term_institutional_flag in the eligibility Input Layer Model is populated with a value other than 0 or 1.

long_term_institutional_flag

invalid

Severity 2

eligibility

multiple open enrollment spanseligibility__multiple_open_enrollment_spans

Checks whether more than one valid open eligibility span exists for the same person_id, member_id, payer, plan, and data_source. Null and the legacy 9999-12-31 alias both represent an open end date. Duplicate stable span identities remain a Structural Data Quality primary-key failure.

person_id, member_id, enrollment_start_date, enrollment_end_date, payer, plan, data_source

consistency

Severity 2

eligibility

overlapping enrollment spanseligibility__overlapping_enrollment_spans

Checks whether a finite eligibility span overlaps another valid span for the same person_id, member_id, payer, plan, and data_source. Every overlap involving at least one finite span is reported on a finite row. Open-versus-open overlaps are reported only by multiple open enrollment spans. Adjacent non-overlapping finite spans pass.

person_id, member_id, enrollment_start_date, enrollment_end_date, payer, plan, data_source

temporal

Severity 2

eligibility

payer_type is invalideligibility__payer_type_invalid

Checks whether payer_type in the eligibility Input Layer Model is populated but not found in Tuva payer type terminology.

payer_type

invalid

Severity 2

eligibility

payer_type is nulleligibility__payer_type_null

Checks whether payer_type is null in the eligibility Input Layer Model.

payer_type

missing

Severity 2

eligibility

race has multiple values per person_ideligibility__multiple_races_per_person

Checks whether the same person_id and data_source identify records with more than one non-null race value in the eligibility Input Layer Model.

race

consistency

Severity 3

eligibility

race is invalideligibility__race_invalid

Checks whether race in the eligibility Input Layer Model is populated but not found in Tuva race terminology.

race

invalid

Severity 3

eligibility

race is nulleligibility__race_null

Checks whether race is null in the eligibility Input Layer Model.

race

missing

Severity 3

eligibility

sex has multiple values per person_ideligibility__multiple_sexes_per_person

Checks whether the same person_id and data_source identify records with more than one exact non-null sex value in the eligibility Input Layer Model. Letter-case variants are distinct values.

sex

consistency

Severity 3

eligibility

sex is invalideligibility__sex_invalid

Checks whether sex in the eligibility Input Layer Model is populated with a value other than the exact lowercase values male, female, or unknown.

sex

invalid

Severity 3

eligibility

sex is nulleligibility__sex_null

Checks whether sex is null in the eligibility Input Layer Model.

sex

missing

Severity 3

encounter

admit_source_code is invalidencounter__admit_source_code_invalid

Checks whether admit_source_code is populated but not found in Tuva admit source terminology.

admit_source_code

invalid

Severity 2

encounter

admit_type_code is invalidencounter__admit_type_code_invalid

Checks whether admit_type_code is populated but not found in Tuva admit type terminology.

admit_type_code

invalid

Severity 2

encounter

discharge_disposition_code is invalidencounter__discharge_disposition_code_invalid

Checks whether discharge_disposition_code is populated but not found in Tuva discharge disposition terminology.

discharge_disposition_code

invalid

Severity 2

encounter

drg_code is invalidencounter__drg_code_invalid

Checks whether drg_code is populated but not found in the DRG terminology indicated by drg_code_type.

drg_code_type, drg_code

invalid

Severity 2

encounter

drg_code is null when drg_code_type is presentencounter__drg_code_null

Checks whether drg_code is null when drg_code_type is populated in the encounter Input Layer Model.

drg_code_type, drg_code

missing

Severity 2

encounter

drg_code_type is invalidencounter__drg_code_type_invalid

Checks whether drg_code_type is populated with a value other than the exact lowercase values ms-drg or apr-drg.

drg_code_type

invalid

Severity 2

encounter

drg_code_type is null when drg_code is presentencounter__drg_code_type_null

Checks whether drg_code_type is null when drg_code is populated in the encounter Input Layer Model.

drg_code_type, drg_code

missing

Severity 2

encounter

encounter_end_date is nullencounter__encounter_end_date_null

Checks whether encounter_end_date is null in the encounter Input Layer Model.

encounter_end_date

missing

Severity 2

encounter

encounter_end_date is out of reasonable rangeencounter__encounter_end_date_out_of_reasonable_range

Checks whether encounter_end_date in the encounter Input Layer Model is before 2000-01-01 or after the current date.

encounter_end_date

invalid

Severity 2

encounter

encounter_start_date is after encounter_end_dateencounter__encounter_start_date_after_encounter_end_date

Checks whether encounter_start_date is after encounter_end_date in the encounter Input Layer Model.

encounter_start_date, encounter_end_date

temporal

Severity 2

encounter

encounter_start_date is nullencounter__encounter_start_date_null

Checks whether encounter_start_date is null in the encounter Input Layer Model.

encounter_start_date

missing

Severity 2

encounter

encounter_start_date is out of reasonable rangeencounter__encounter_start_date_out_of_reasonable_range

Checks whether encounter_start_date in the encounter Input Layer Model is before 2000-01-01 or after the current date.

encounter_start_date

invalid

Severity 2

encounter

encounter_type is invalidencounter__encounter_type_invalid

Checks whether encounter_type is populated but does not exactly match a lowercase value in Tuva encounter type terminology.

encounter_type

invalid

Severity 2

encounter

facility_npi is invalidencounter__facility_npi_invalid

Checks whether facility_npi is populated but not found in Tuva provider data.

facility_npi

invalid

Severity 2

encounter

ingest_datetime is out of reasonable rangeencounter__ingest_datetime_out_of_reasonable_range

Checks whether a populated ingest_datetime in the encounter Input Layer Model is before 2000-01-01 or after the current date.

ingest_datetime

invalid

Severity 2

encounter

patient_id is nullencounter__patient_id_null

Checks whether patient_id is null in the encounter Input Layer Model.

patient_id

missing

Severity 2

encounter

patient_id not found in patient tableencounter__patient_id_not_in_patient

Checks whether patient_id values in the encounter Input Layer Model have a corresponding patient_id in the patient Input Layer Model for the same data_source.

patient_id, data_source

referential

Severity 2

encounter

person_id and patient_id pair not found in patient tableencounter__person_patient_pair_not_in_patient

Checks whether populated person_id and patient_id values each exist in the patient Input Layer Model for the same data_source but their exact pair does not.

person_id, patient_id, data_source

referential

Severity 2

encounter

person_id is nullencounter__person_id_null

Checks whether person_id is null in the encounter Input Layer Model.

person_id

missing

Severity 2

encounter

person_id not found in patient tableencounter__person_id_not_in_patient

Checks whether person_id values in the encounter Input Layer Model have a corresponding person_id in the patient Input Layer Model for the same data_source.

person_id, data_source

referential

Severity 2

encounter

primary_diagnosis_code is invalidencounter__primary_diagnosis_code_invalid

Checks whether primary_diagnosis_code is populated but not found in the ICD terminology indicated by primary_diagnosis_code_type.

primary_diagnosis_code_type, primary_diagnosis_code

invalid

Severity 2

encounter

primary_diagnosis_code is null when primary_diagnosis_code_type is presentencounter__primary_diagnosis_code_null

Checks whether primary_diagnosis_code is null when primary_diagnosis_code_type is populated in the encounter Input Layer Model.

primary_diagnosis_code_type, primary_diagnosis_code

missing

Severity 2

encounter

primary_diagnosis_code_type is invalidencounter__primary_diagnosis_code_type_invalid

Checks whether primary_diagnosis_code_type is populated with a value other than the exact lowercase values icd-9-cm or icd-10-cm.

primary_diagnosis_code_type

invalid

Severity 2

encounter

primary_diagnosis_code_type is null when primary_diagnosis_code is presentencounter__primary_diagnosis_code_type_null

Checks whether primary_diagnosis_code_type is null when primary_diagnosis_code is populated in the encounter Input Layer Model.

primary_diagnosis_code_type, primary_diagnosis_code

missing

Severity 2

immunization

encounter_id not found in encounter tableimmunization__encounter_id_not_in_encounter

Checks whether populated encounter_id values in the immunization Input Layer Model have a corresponding encounter_id in the encounter Input Layer Model for the same data_source.

encounter_id, data_source

referential

Severity 2

immunization

encounter_id, person_id, and patient_id combination not found in encounter tableimmunization__encounter_person_patient_pair_not_in_encounter

Checks whether a populated encounter_id exists for the data_source and the populated person_id and patient_id pair exists in the patient Input Layer Model, but the encounter is not assigned to that exact pair in the encounter Input Layer Model.

encounter_id, person_id, patient_id, data_source

referential

Severity 2

immunization

ingest_datetime is out of reasonable rangeimmunization__ingest_datetime_out_of_reasonable_range

Checks whether a populated ingest_datetime in the immunization Input Layer Model is before 2000-01-01 or after the current date.

ingest_datetime

invalid

Severity 2

immunization

occurrence date is nullimmunization__occurrence_date_null

Checks whether occurrence_date is null on an immunization record.

occurrence_date

missing

Severity 2

immunization

occurrence_date is outside the supported date rangeimmunization__occurrence_date_outside_supported_date_range

Checks whether a populated occurrence_date in the immunization Input Layer Model is before 1900-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

occurrence_date

invalid

Severity 2

immunization

patient_id is nullimmunization__patient_id_null

Checks whether patient_id is null in the immunization Input Layer Model.

patient_id

missing

Severity 2

immunization

patient_id not found in patient tableimmunization__patient_id_not_in_patient

Checks whether patient_id values in the immunization Input Layer Model have a corresponding patient_id in the patient Input Layer Model for the same data_source.

patient_id, data_source

referential

Severity 2

immunization

person_id and patient_id pair not found in patient tableimmunization__person_patient_pair_not_in_patient

Checks whether populated person_id and patient_id values each exist in the patient Input Layer Model for the same data_source but their exact pair does not.

person_id, patient_id, data_source

referential

Severity 2

immunization

person_id is nullimmunization__person_id_null

Checks whether person_id is null in the immunization Input Layer Model.

person_id

missing

Severity 2

immunization

person_id not found in patient tableimmunization__person_id_not_in_patient

Checks whether person_id values in the immunization Input Layer Model have a corresponding person_id in the patient Input Layer Model for the same data_source.

person_id, data_source

referential

Severity 2

immunization

source code is invalidimmunization__source_code_invalid

Checks whether a populated CVX source_code on an immunization record is absent from Tuva CVX terminology. Other code systems are not applicable.

source_code_type, source_code

invalid

Severity 2

immunization

source code is null when source code type presentimmunization__source_code_null_when_source_code_type_present

Checks whether source_code is null when source_code_type is populated on an immunization record.

source_code_type, source_code

missing

Severity 2

immunization

source code type is null when source code presentimmunization__source_code_type_null_when_source_code_present

Checks whether source_code_type is null when source_code is populated on an immunization record.

source_code_type, source_code

missing

Severity 2

immunization

status is invalidimmunization__status_invalid

Checks whether a populated immunization status is absent from Tuva immunization-status terminology.

status

invalid

Severity 2

immunization

status reason is invalidimmunization__status_reason_invalid

Checks whether a populated immunization status_reason is absent from Tuva immunization-status-reason terminology.

status_reason

invalid

Severity 2

immunization

status reason present for completed or error statusimmunization__status_reason_present_for_completed_or_error_status

Checks whether a status_reason is populated for a recognized immunization status other than not-done.

status, status_reason

consistency

Severity 2

lab_result

accession_number is nulllab_result__accession_number_null

Checks whether accession_number is null in the lab_result Input Layer Model.

accession_number

missing

Severity 3

lab_result

collection datetime is after result datetimelab_result__collection_datetime_after_result_datetime

Checks whether a populated collection_datetime occurs after result_datetime.

collection_datetime, result_datetime

temporal

Severity 2

lab_result

collection datetime is out of reasonable rangelab_result__collection_datetime_out_of_reasonable_range

Checks whether a populated collection_datetime is before 2000-01-01 or after the current date.

collection_datetime

invalid

Severity 2

lab_result

encounter_id not found in encounter tablelab_result__encounter_id_not_in_encounter

Checks whether populated encounter_id values in the lab_result Input Layer Model have a corresponding encounter_id in the encounter Input Layer Model for the same data_source.

encounter_id, data_source

referential

Severity 2

lab_result

encounter_id, person_id, and patient_id combination not found in encounter tablelab_result__encounter_person_patient_pair_not_in_encounter

Checks whether a populated encounter_id exists for the data_source and the populated person_id and patient_id pair exists in the patient Input Layer Model, but the encounter is not assigned to that exact pair in the encounter Input Layer Model.

encounter_id, person_id, patient_id, data_source

referential

Severity 2

lab_result

ingest_datetime is out of reasonable rangelab_result__ingest_datetime_out_of_reasonable_range

Checks whether a populated ingest_datetime in the lab_result Input Layer Model is before 2000-01-01 or after the current date.

ingest_datetime

invalid

Severity 2

lab_result

patient_id is nulllab_result__patient_id_null

Checks whether patient_id is null in the lab_result Input Layer Model.

patient_id

missing

Severity 2

lab_result

patient_id not found in patient tablelab_result__patient_id_not_in_patient

Checks whether patient_id values in the lab_result Input Layer Model have a corresponding patient_id in the patient Input Layer Model for the same data_source.

patient_id, data_source

referential

Severity 2

lab_result

person_id and patient_id pair not found in patient tablelab_result__person_patient_pair_not_in_patient

Checks whether populated person_id and patient_id values each exist in the patient Input Layer Model for the same data_source but their exact pair does not.

person_id, patient_id, data_source

referential

Severity 2

lab_result

person_id is nulllab_result__person_id_null

Checks whether person_id is null in the lab_result Input Layer Model.

person_id

missing

Severity 2

lab_result

person_id not found in patient tablelab_result__person_id_not_in_patient

Checks whether person_id values in the lab_result Input Layer Model have a corresponding person_id in the patient Input Layer Model for the same data_source.

person_id, data_source

referential

Severity 2

lab_result

result datetime is out of reasonable rangelab_result__result_datetime_out_of_reasonable_range

Checks whether a populated result_datetime is before 2000-01-01 or after the current date.

result_datetime

invalid

Severity 2

lab_result

source order code is invalidlab_result__source_order_code_invalid

Checks whether a populated source_order_code is absent from the corresponding terminology when source_order_type identifies LOINC or SNOMED CT without regard to letter case. Every other source_order_type, including a source-system-specific name, is not applicable to this code-validity test.

source_order_type, source_order_code

invalid

Severity 2

lab_result

source order code is null when source order type presentlab_result__source_order_code_null_when_source_order_type_present

Checks whether source_order_code is null when source_order_type is populated on a lab result.

source_order_type, source_order_code

missing

Severity 2

lab_result

source order type is null when source order code presentlab_result__source_order_type_null_when_source_order_code_present

Checks whether source_order_type is null when source_order_code is populated on a lab result.

source_order_type, source_order_code

missing

Severity 2

lab_result

source_component_code is invalidlab_result__source_component_code_invalid

Checks whether a populated source_component_code is absent from the corresponding terminology when source_component_type identifies LOINC or SNOMED CT without regard to letter case. Every other source_component_type, including a source-system-specific name, is not applicable to this code-validity test.

source_component_type, source_component_code

invalid

Severity 2

lab_result

source_component_type is null when source_component_code presentlab_result__source_component_type_null_when_source_component_code_present

Checks whether source_component_type is null when source_component_code is populated in the lab_result Input Layer Model.

source_component_type, source_component_code

missing

Severity 2

location

ingest_datetime is out of reasonable rangelocation__ingest_datetime_out_of_reasonable_range

Checks whether a populated ingest_datetime in the location Input Layer Model is before 2000-01-01 or after the current date.

ingest_datetime

invalid

Severity 2

location

NPI is invalidlocation__npi_invalid

Checks whether npi is populated in the location Input Layer Model but not found in Tuva provider data.

npi

invalid

Severity 3

medical_claim

admission_date has multiple values per inpatient claimmedical_claim__admission_date_has_multiple_values_per_inpatient_claim

Checks whether an inpatient facility claim_id has more than one non-null admission_date across claim lines.

admission_date

consistency

Severity 2

medical_claim

admission_date is after discharge_datemedical_claim__admission_date_after_discharge_date

Checks whether admission_date is after discharge_date on a medical claim line.

admission_date, discharge_date

temporal

Severity 2

medical_claim

admission_date is null for inpatient claimmedical_claim__admission_date_null_for_inpatient_claim

Checks whether admission_date is null on an inpatient facility claim line.

admission_date

missing

Severity 2

medical_claim

admission_date is out of reasonable rangemedical_claim__admission_date_out_of_reasonable_range

Checks whether admission_date on a medical claim line is before 2000-01-01 or after the current date.

admission_date

invalid

Severity 2

medical_claim

admit source code has multiple values per inpatient claimmedical_claim__admit_source_code_has_multiple_values_per_inpatient_claim

Checks whether a multi-line inpatient medical claim has inconsistent admit_source_code values, including a mix of null and non-null values.

admit_source_code

consistency

Severity 2

medical_claim

admit type code has multiple values per inpatient claimmedical_claim__admit_type_code_has_multiple_values_per_inpatient_claim

Checks whether a multi-line inpatient medical claim has inconsistent admit_type_code values, including a mix of null and non-null values.

admit_type_code

consistency

Severity 2

medical_claim

admit_source_code is invalidmedical_claim__admit_source_code_invalid

Checks whether admit_source_code is populated on an institutional medical claim line but not found in Tuva admit source terminology.

admit_source_code

invalid

Severity 2

medical_claim

admit_type_code is invalidmedical_claim__admit_type_code_invalid

Checks whether admit_type_code is populated on an institutional medical claim line but not found in Tuva admit type terminology.

admit_type_code

invalid

Severity 2

medical_claim

allowed_amount is less than zeromedical_claim__allowed_amount_lt_zero

Checks whether allowed_amount is less than zero on a medical claim line.

allowed_amount

invalid

Severity 2

medical_claim

allowed_amount is nullmedical_claim__allowed_amount_null

Checks whether allowed_amount is null on a medical claim line.

allowed_amount

missing

Severity 2

medical_claim

bill_type_code has multiple values per institutional claim_idmedical_claim__bill_type_code_count_ne_one_for_institutional_claim

Checks whether a multi-line institutional medical claim with at least one populated bill_type_code contains more than one distinct populated bill_type_code.

bill_type_code

consistency

Severity 2

medical_claim

bill_type_code is invalidmedical_claim__bill_type_code_invalid

Checks whether bill_type_code is populated on an institutional medical claim line but not found in Tuva bill type terminology.

bill_type_code

invalid

Severity 2

medical_claim

bill_type_code is null for institutional claimmedical_claim__bill_type_code_null_for_institutional_claim

Checks whether bill_type_code is null on an institutional medical claim line.

bill_type_code

missing

Severity 2

medical_claim

billing npi has multiple values per claimmedical_claim__billing_npi_has_multiple_values_per_claim

Checks whether a multi-line medical claim has inconsistent billing_npi values, including a mix of null and non-null values.

billing_npi

consistency

Severity 2

medical_claim

billing_npi is invalidmedical_claim__billing_npi_invalid

Checks whether billing_npi is populated but not found in Tuva provider data.

billing_npi

invalid

Severity 2

medical_claim

billing_npi is nullmedical_claim__billing_npi_null

Checks whether billing_npi is null on a medical claim line.

billing_npi

missing

Severity 2

medical_claim

claim end date has multiple values per claimmedical_claim__claim_end_date_has_multiple_values_per_claim

Checks whether a multi-line medical claim has inconsistent claim_end_date values, including a mix of null and non-null values.

claim_end_date

consistency

Severity 1

medical_claim

claim line number is not positivemedical_claim__claim_line_number_not_positive

Checks whether a populated claim_line_number on a medical claim is zero or negative.

claim_line_number

invalid

Severity 1

medical_claim

claim start date has multiple values per claimmedical_claim__claim_start_date_has_multiple_values_per_claim

Checks whether a multi-line medical claim has inconsistent claim_start_date values, including a mix of null and non-null values.

claim_start_date

consistency

Severity 1

medical_claim

claim_end_date is nullmedical_claim__claim_end_date_null

Checks whether claim_end_date is null on a medical claim line.

claim_end_date

missing

Severity 1

medical_claim

claim_end_date is out of reasonable rangemedical_claim__claim_end_date_out_of_reasonable_range

Checks whether claim_end_date on a medical claim line is before 2000-01-01 or after the current date.

claim_end_date

invalid

Severity 2

medical_claim

claim_line_end_date is nullmedical_claim__claim_line_end_date_null

Checks whether claim_line_end_date is null on a medical claim line.

claim_line_end_date

missing

Severity 1

medical_claim

claim_line_end_date is out of reasonable rangemedical_claim__claim_line_end_date_out_of_reasonable_range

Checks whether claim_line_end_date on a medical claim line is before 2000-01-01 or after the current date.

claim_line_end_date

invalid

Severity 2

medical_claim

claim_line_start_date is after claim_line_end_datemedical_claim__claim_line_start_after_claim_line_end

Checks whether claim_line_start_date is after claim_line_end_date on a medical claim line.

claim_line_start_date, claim_line_end_date

temporal

Severity 2

medical_claim

claim_line_start_date is nullmedical_claim__claim_line_start_date_null

Checks whether claim_line_start_date is null on a medical claim line.

claim_line_start_date

missing

Severity 1

medical_claim

claim_line_start_date is out of reasonable rangemedical_claim__claim_line_start_date_out_of_reasonable_range

Checks whether claim_line_start_date on a medical claim line is before 2000-01-01 or after the current date.

claim_line_start_date

invalid

Severity 2

medical_claim

claim_start_date is after claim_end_datemedical_claim__claim_start_after_claim_end

Checks whether claim_start_date is after claim_end_date on a medical claim line.

claim_start_date, claim_end_date

temporal

Severity 2

medical_claim

claim_start_date is nullmedical_claim__claim_start_date_null

Checks whether claim_start_date is null on a medical claim line.

claim_start_date

missing

Severity 1

medical_claim

claim_start_date is out of reasonable rangemedical_claim__claim_start_date_out_of_reasonable_range

Checks whether claim_start_date on a medical claim line is before 2000-01-01 or after the current date.

claim_start_date

invalid

Severity 2

medical_claim

claim_type has multiple values per claim_idmedical_claim__claim_type_count_ne_one_per_claim

Checks whether a multi-line medical claim with at least one populated claim_type contains more than one distinct exact claim_type value, including values that differ only by letter case.

claim_type

consistency

Severity 1

medical_claim

claim_type is invalidmedical_claim__claim_type_invalid

Checks whether claim_type is populated with a value other than the exact lowercase values professional, institutional, or undetermined.

claim_type

invalid

Severity 1

medical_claim

claim_type is nullmedical_claim__claim_type_null

Checks whether claim_type is null on a medical claim line.

claim_type

missing

Severity 1

medical_claim

diagnosis code type has multiple values per claimmedical_claim__diagnosis_code_type_has_multiple_values_per_claim

Checks whether diagnosis-bearing lines in a multi-line medical claim have inconsistent exact diagnosis_code_type values, including values that differ only by letter case or a mix of null and non-null values.

diagnosis_code_type, diagnosis_code_1, diagnosis_code_2, diagnosis_code_3, diagnosis_code_4, diagnosis_code_5, diagnosis_code_6, diagnosis_code_7, diagnosis_code_8, diagnosis_code_9, diagnosis_code_10, diagnosis_code_11, diagnosis_code_12, diagnosis_code_13, diagnosis_code_14, diagnosis_code_15, diagnosis_code_16, diagnosis_code_17, diagnosis_code_18, diagnosis_code_19, diagnosis_code_20, diagnosis_code_21, diagnosis_code_22, diagnosis_code_23, diagnosis_code_24, diagnosis_code_25

consistency

Severity 2

medical_claim

diagnosis_code has multiple values per position for institutional claimmedical_claim__diagnosis_code_count_gt_one_per_position_for_institutional_claim

Checks whether an institutional claim_id has more than one distinct non-null diagnosis code in the same diagnosis position across claim lines.

diagnosis_code_1, diagnosis_code_2, diagnosis_code_3, diagnosis_code_4, diagnosis_code_5, diagnosis_code_6, diagnosis_code_7, diagnosis_code_8, diagnosis_code_9, diagnosis_code_10, diagnosis_code_11, diagnosis_code_12, diagnosis_code_13, diagnosis_code_14, diagnosis_code_15, diagnosis_code_16, diagnosis_code_17, diagnosis_code_18, diagnosis_code_19, diagnosis_code_20, diagnosis_code_21, diagnosis_code_22, diagnosis_code_23, diagnosis_code_24, diagnosis_code_25

consistency

Severity 2

medical_claim

diagnosis_code_1 is invalidmedical_claim__diagnosis_code_1_invalid

Checks whether diagnosis_code_1 is populated, diagnosis_code_type equals the exact lowercase value icd-9-cm or icd-10-cm, and the code is not found in the corresponding ICD terminology.

diagnosis_code_type, diagnosis_code_1

invalid

Severity 2

medical_claim

diagnosis_code_1 is nullmedical_claim__diagnosis_code_1_null

Checks whether diagnosis_code_1 is null on a medical claim line.

diagnosis_code_1

missing

Severity 2

medical_claim

diagnosis_code_2 to diagnosis_code_25 is invalidmedical_claim__diagnosis_code_2_to_25_invalid

Checks whether diagnosis_code_2 through diagnosis_code_25 contain populated codes, diagnosis_code_type equals the exact lowercase value icd-9-cm or icd-10-cm, and at least one code is not found in the corresponding ICD terminology.

diagnosis_code_type, diagnosis_code_2, diagnosis_code_3, diagnosis_code_4, diagnosis_code_5, diagnosis_code_6, diagnosis_code_7, diagnosis_code_8, diagnosis_code_9, diagnosis_code_10, diagnosis_code_11, diagnosis_code_12, diagnosis_code_13, diagnosis_code_14, diagnosis_code_15, diagnosis_code_16, diagnosis_code_17, diagnosis_code_18, diagnosis_code_19, diagnosis_code_20, diagnosis_code_21, diagnosis_code_22, diagnosis_code_23, diagnosis_code_24, diagnosis_code_25

invalid

Severity 2

medical_claim

diagnosis_code_type is invalidmedical_claim__diagnosis_code_type_invalid

Checks whether diagnosis_code_type is populated with a value other than the exact lowercase values icd-9-cm or icd-10-cm.

diagnosis_code_type

invalid

Severity 2

medical_claim

diagnosis_code_type is null when diagnosis_code is presentmedical_claim__diagnosis_code_type_null_when_diagnosis_code_present

Checks whether diagnosis_code_type is null when any diagnosis code is populated on a medical claim line.

diagnosis_code_type, diagnosis_code_1, diagnosis_code_2, diagnosis_code_3, diagnosis_code_4, diagnosis_code_5, diagnosis_code_6, diagnosis_code_7, diagnosis_code_8, diagnosis_code_9, diagnosis_code_10, diagnosis_code_11, diagnosis_code_12, diagnosis_code_13, diagnosis_code_14, diagnosis_code_15, diagnosis_code_16, diagnosis_code_17, diagnosis_code_18, diagnosis_code_19, diagnosis_code_20, diagnosis_code_21, diagnosis_code_22, diagnosis_code_23, diagnosis_code_24, diagnosis_code_25

missing

Severity 2

medical_claim

discharge disposition code has multiple values per inpatient claimmedical_claim__discharge_disposition_code_has_multiple_values_per_inpatient_claim

Checks whether a multi-line inpatient medical claim has inconsistent discharge_disposition_code values, including a mix of null and non-null values.

discharge_disposition_code

consistency

Severity 2

medical_claim

discharge_date has multiple values per inpatient claimmedical_claim__discharge_date_has_multiple_values_per_inpatient_claim

Checks whether an inpatient facility claim_id has more than one non-null discharge_date across claim lines.

discharge_date

consistency

Severity 2

medical_claim

discharge_date is null for inpatient claimmedical_claim__discharge_date_null_for_inpatient_claim

Checks whether discharge_date is null on an inpatient facility claim line.

discharge_date

missing

Severity 2

medical_claim

discharge_date is out of reasonable rangemedical_claim__discharge_date_out_of_reasonable_range

Checks whether discharge_date on a medical claim line is before 2000-01-01 or after the current date.

discharge_date

invalid

Severity 2

medical_claim

discharge_disposition_code is invalidmedical_claim__discharge_disposition_code_invalid

Checks whether discharge_disposition_code is populated on an institutional medical claim line but not found in Tuva discharge disposition terminology.

discharge_disposition_code

invalid

Severity 2

medical_claim

drg code type has multiple values per acute inpatient claimmedical_claim__drg_code_type_has_multiple_values_per_acute_inpatient_claim

Checks whether a multi-line acute inpatient medical claim has inconsistent exact drg_code_type values, including values that differ only by letter case or a mix of null and non-null values.

drg_code_type

consistency

Severity 2

medical_claim

drg_code has multiple values per acute inpatient claim_idmedical_claim__drg_code_count_ne_one_for_acute_inpatient_claim

Checks whether a multi-line acute inpatient medical claim with at least one populated drg_code contains more than one distinct populated drg_code.

drg_code

consistency

Severity 2

medical_claim

drg_code is invalidmedical_claim__drg_code_invalid

Checks whether drg_code is populated on an institutional medical claim line, drg_code_type equals the exact lowercase value ms-drg or apr-drg, and the code is not found in the corresponding DRG terminology.

drg_code_type, drg_code

invalid

Severity 2

medical_claim

drg_code is null for acute inpatient claimmedical_claim__drg_code_null_for_acute_inpatient_claim

Checks whether drg_code is null on an acute inpatient claim line.

drg_code

missing

Severity 2

medical_claim

drg_code_type is invalidmedical_claim__drg_code_type_invalid

Checks whether drg_code_type is populated with a value other than the exact lowercase values ms-drg or apr-drg.

drg_code_type

invalid

Severity 2

medical_claim

drg_code_type is null when drg_code is presentmedical_claim__drg_code_type_null_when_drg_code_present

Checks whether drg_code_type is null when drg_code is populated on a medical claim line.

drg_code_type, drg_code

missing

Severity 2

medical_claim

facility_npi has multiple values per claim_idmedical_claim__facility_npi_has_multiple_values_per_claim

Checks whether a claim_id has more than one non-null facility_npi across claim lines.

facility_npi

consistency

Severity 2

medical_claim

facility_npi is invalidmedical_claim__facility_npi_invalid

Checks whether facility_npi is populated but not found in Tuva provider data.

facility_npi

invalid

Severity 2

medical_claim

facility_npi is null for inpatient claimmedical_claim__facility_npi_null_for_inpatient_claim

Checks whether facility_npi is null on an inpatient facility claim line.

facility_npi

missing

Severity 2

medical_claim

file_date is outside the supported date rangemedical_claim__file_date_outside_supported_date_range

Checks whether a populated file_date in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

file_date

invalid

Severity 2

medical_claim

hcpcs_code is null for professional claimmedical_claim__hcpcs_code_null_for_professional_claim

Checks whether hcpcs_code is null on a professional claim line.

hcpcs_code

missing

Severity 2

medical_claim

in_network_flag is invalidmedical_claim__in_network_flag_invalid

Checks whether in_network_flag in the medical_claim Input Layer Model is populated with a value other than 0 or 1.

in_network_flag

invalid

Severity 2

medical_claim

ingest_datetime is out of reasonable rangemedical_claim__ingest_datetime_out_of_reasonable_range

Checks whether a populated ingest_datetime in the medical_claim Input Layer Model is before 2000-01-01 or after the current date.

ingest_datetime

invalid

Severity 2

medical_claim

institutional indicators present for professional claimmedical_claim__institutional_indicators_present_for_professional_claim

Checks whether a professional claim line contains a populated bill_type_code, drg_code, admit_type_code, admit_source_code, discharge_disposition_code, or revenue_center_code.

claim_type, bill_type_code, drg_code, admit_type_code, admit_source_code, discharge_disposition_code, revenue_center_code

consistency

Severity 2

medical_claim

member id has multiple values per claimmedical_claim__member_id_has_multiple_values_per_claim

Checks whether a multi-line medical claim has inconsistent member_id values, including a mix of null and non-null values.

member_id

consistency

Severity 2

medical_claim

no matching eligibility spanmedical_claim__no_matching_eligibility_span

Checks whether a medical claim line with a complete person_id, member_id, payer, plan, and data_source identity and a populated inferred claim date has no eligibility span for the same complete identity whose covered calendar months include the inferred claim date month. Rows whose inferred date is outside the valid range from 2000-01-01 through the current date, outside the member-month spine from 1900-01 through 2100-12, or after tuva_last_run are not applicable. Eligibility coverage is evaluated only through the calendar month containing tuva_last_run: null and the legacy 9999-12-31 alias use that as-of boundary, and a later finite enrollment_end_date is capped to the same boundary. The inferred claim date uses claim_line_start_date, then claim_start_date, then admission_date.

person_id, member_id, payer, plan, claim_line_start_date, claim_start_date, admission_date, data_source

referential

Severity 2

medical_claim

paid date is nullmedical_claim__paid_date_null

Checks whether paid_date is null on a medical claim line.

paid_date

missing

Severity 3

medical_claim

paid date is out of reasonable rangemedical_claim__paid_date_out_of_reasonable_range

Checks whether a populated paid_date on a medical claim line is before 2000-01-01 or after the current date.

paid_date

invalid

Severity 2

medical_claim

paid_amount is greater than allowed_amountmedical_claim__paid_amount_gt_allowed_amount

Checks whether paid_amount is greater than allowed_amount on a medical claim line.

allowed_amount, paid_amount

consistency

Severity 2

medical_claim

paid_amount is less than zeromedical_claim__paid_amount_lt_zero

Checks whether paid_amount is less than zero on a medical claim line.

paid_amount

invalid

Severity 2

medical_claim

paid_amount is nullmedical_claim__paid_amount_null

Checks whether paid_amount is null on a medical claim line.

paid_amount

missing

Severity 2

medical_claim

paid_date before claim_end_datemedical_claim__paid_date_before_claim_end_date

Checks whether a populated paid_date occurs before claim_end_date on a medical claim line.

paid_date, claim_end_date

temporal

Severity 2

medical_claim

payer has multiple values per claimmedical_claim__payer_has_multiple_values_per_claim

Checks whether a multi-line medical claim has inconsistent payer values, including a mix of null and non-null values.

payer

consistency

Severity 2

medical_claim

person_id has multiple values per claimmedical_claim__multiple_person_ids_per_claim

Checks whether a claim_id is associated with more than one person_id within the same data_source.

person_id

consistency

Severity 1

medical_claim

person_id is nullmedical_claim__person_id_null

Checks whether person_id is null on a medical claim line.

person_id

missing

Severity 1

medical_claim

place_of_service_code is invalidmedical_claim__place_of_service_code_invalid

Checks whether place_of_service_code is populated on a professional medical claim line but not found in Tuva place of service terminology.

place_of_service_code

invalid

Severity 2

medical_claim

place_of_service_code is null for professional claimmedical_claim__place_of_service_code_null_for_professional_claim

Checks whether place_of_service_code is null on a professional claim line.

place_of_service_code

missing

Severity 2

medical_claim

place_of_service_code present for institutional claimmedical_claim__place_of_service_code_present_for_institutional_claim

Checks whether place_of_service_code is populated on an institutional claim line.

place_of_service_code

consistency

Severity 2

medical_claim

plan has multiple values per claimmedical_claim__plan_has_multiple_values_per_claim

Checks whether a multi-line medical claim has inconsistent plan values, including a mix of null and non-null values.

plan

consistency

Severity 2

medical_claim

procedure code type has multiple values per claimmedical_claim__procedure_code_type_has_multiple_values_per_claim

Checks whether procedure-bearing lines in a multi-line medical claim have inconsistent exact procedure_code_type values, including values that differ only by letter case or a mix of null and non-null values.

procedure_code_type, procedure_code_1, procedure_code_2, procedure_code_3, procedure_code_4, procedure_code_5, procedure_code_6, procedure_code_7, procedure_code_8, procedure_code_9, procedure_code_10, procedure_code_11, procedure_code_12, procedure_code_13, procedure_code_14, procedure_code_15, procedure_code_16, procedure_code_17, procedure_code_18, procedure_code_19, procedure_code_20, procedure_code_21, procedure_code_22, procedure_code_23, procedure_code_24, procedure_code_25

consistency

Severity 2

medical_claim

procedure_code_1 to procedure_code_25 is invalidmedical_claim__procedure_code_1_to_25_invalid

Checks whether procedure_code_1 through procedure_code_25 contain populated codes, procedure_code_type equals the exact lowercase value icd-9-pcs or icd-10-pcs, and at least one code is not found in the corresponding ICD procedure terminology.

procedure_code_type, procedure_code_1, procedure_code_2, procedure_code_3, procedure_code_4, procedure_code_5, procedure_code_6, procedure_code_7, procedure_code_8, procedure_code_9, procedure_code_10, procedure_code_11, procedure_code_12, procedure_code_13, procedure_code_14, procedure_code_15, procedure_code_16, procedure_code_17, procedure_code_18, procedure_code_19, procedure_code_20, procedure_code_21, procedure_code_22, procedure_code_23, procedure_code_24, procedure_code_25

invalid

Severity 2

medical_claim

procedure_code_type is invalidmedical_claim__procedure_code_type_invalid

Checks whether procedure_code_type is populated with a value other than the exact lowercase values icd-9-pcs or icd-10-pcs.

procedure_code_type

invalid

Severity 2

medical_claim

procedure_code_type is null when procedure_code is presentmedical_claim__procedure_code_type_null_when_procedure_code_present

Checks whether procedure_code_type is null when any procedure code is populated on a medical claim line.

procedure_code_type, procedure_code_1, procedure_code_2, procedure_code_3, procedure_code_4, procedure_code_5, procedure_code_6, procedure_code_7, procedure_code_8, procedure_code_9, procedure_code_10, procedure_code_11, procedure_code_12, procedure_code_13, procedure_code_14, procedure_code_15, procedure_code_16, procedure_code_17, procedure_code_18, procedure_code_19, procedure_code_20, procedure_code_21, procedure_code_22, procedure_code_23, procedure_code_24, procedure_code_25

missing

Severity 2

medical_claim

procedure_date_1 is outside the supported date rangemedical_claim__procedure_date_1_outside_supported_date_range

Checks whether a populated procedure_date_1 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_1

invalid

Severity 2

medical_claim

procedure_date_10 is outside the supported date rangemedical_claim__procedure_date_10_outside_supported_date_range

Checks whether a populated procedure_date_10 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_10

invalid

Severity 2

medical_claim

procedure_date_11 is outside the supported date rangemedical_claim__procedure_date_11_outside_supported_date_range

Checks whether a populated procedure_date_11 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_11

invalid

Severity 2

medical_claim

procedure_date_12 is outside the supported date rangemedical_claim__procedure_date_12_outside_supported_date_range

Checks whether a populated procedure_date_12 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_12

invalid

Severity 2

medical_claim

procedure_date_13 is outside the supported date rangemedical_claim__procedure_date_13_outside_supported_date_range

Checks whether a populated procedure_date_13 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_13

invalid

Severity 2

medical_claim

procedure_date_14 is outside the supported date rangemedical_claim__procedure_date_14_outside_supported_date_range

Checks whether a populated procedure_date_14 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_14

invalid

Severity 2

medical_claim

procedure_date_15 is outside the supported date rangemedical_claim__procedure_date_15_outside_supported_date_range

Checks whether a populated procedure_date_15 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_15

invalid

Severity 2

medical_claim

procedure_date_16 is outside the supported date rangemedical_claim__procedure_date_16_outside_supported_date_range

Checks whether a populated procedure_date_16 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_16

invalid

Severity 2

medical_claim

procedure_date_17 is outside the supported date rangemedical_claim__procedure_date_17_outside_supported_date_range

Checks whether a populated procedure_date_17 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_17

invalid

Severity 2

medical_claim

procedure_date_18 is outside the supported date rangemedical_claim__procedure_date_18_outside_supported_date_range

Checks whether a populated procedure_date_18 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_18

invalid

Severity 2

medical_claim

procedure_date_19 is outside the supported date rangemedical_claim__procedure_date_19_outside_supported_date_range

Checks whether a populated procedure_date_19 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_19

invalid

Severity 2

medical_claim

procedure_date_2 is outside the supported date rangemedical_claim__procedure_date_2_outside_supported_date_range

Checks whether a populated procedure_date_2 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_2

invalid

Severity 2

medical_claim

procedure_date_20 is outside the supported date rangemedical_claim__procedure_date_20_outside_supported_date_range

Checks whether a populated procedure_date_20 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_20

invalid

Severity 2

medical_claim

procedure_date_21 is outside the supported date rangemedical_claim__procedure_date_21_outside_supported_date_range

Checks whether a populated procedure_date_21 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_21

invalid

Severity 2

medical_claim

procedure_date_22 is outside the supported date rangemedical_claim__procedure_date_22_outside_supported_date_range

Checks whether a populated procedure_date_22 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_22

invalid

Severity 2

medical_claim

procedure_date_23 is outside the supported date rangemedical_claim__procedure_date_23_outside_supported_date_range

Checks whether a populated procedure_date_23 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_23

invalid

Severity 2

medical_claim

procedure_date_24 is outside the supported date rangemedical_claim__procedure_date_24_outside_supported_date_range

Checks whether a populated procedure_date_24 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_24

invalid

Severity 2

medical_claim

procedure_date_25 is outside the supported date rangemedical_claim__procedure_date_25_outside_supported_date_range

Checks whether a populated procedure_date_25 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_25

invalid

Severity 2

medical_claim

procedure_date_3 is outside the supported date rangemedical_claim__procedure_date_3_outside_supported_date_range

Checks whether a populated procedure_date_3 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_3

invalid

Severity 2

medical_claim

procedure_date_4 is outside the supported date rangemedical_claim__procedure_date_4_outside_supported_date_range

Checks whether a populated procedure_date_4 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_4

invalid

Severity 2

medical_claim

procedure_date_5 is outside the supported date rangemedical_claim__procedure_date_5_outside_supported_date_range

Checks whether a populated procedure_date_5 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_5

invalid

Severity 2

medical_claim

procedure_date_6 is outside the supported date rangemedical_claim__procedure_date_6_outside_supported_date_range

Checks whether a populated procedure_date_6 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_6

invalid

Severity 2

medical_claim

procedure_date_7 is outside the supported date rangemedical_claim__procedure_date_7_outside_supported_date_range

Checks whether a populated procedure_date_7 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_7

invalid

Severity 2

medical_claim

procedure_date_8 is outside the supported date rangemedical_claim__procedure_date_8_outside_supported_date_range

Checks whether a populated procedure_date_8 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_8

invalid

Severity 2

medical_claim

procedure_date_9 is outside the supported date rangemedical_claim__procedure_date_9_outside_supported_date_range

Checks whether a populated procedure_date_9 in the medical_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

procedure_date_9

invalid

Severity 2

medical_claim

rendering_npi is invalidmedical_claim__rendering_npi_invalid

Checks whether rendering_npi is populated but not found in Tuva provider data.

rendering_npi

invalid

Severity 2

medical_claim

rendering_npi is nullmedical_claim__rendering_npi_null

Checks whether rendering_npi is null on a medical claim line.

rendering_npi

missing

Severity 2

medical_claim

revenue_center_code is invalidmedical_claim__revenue_center_code_invalid

Checks whether revenue_center_code is populated on an institutional medical claim line but not found in Tuva revenue center terminology.

revenue_center_code

invalid

Severity 2

medical_claim

revenue_center_code is null for institutional claimmedical_claim__revenue_center_code_null_for_institutional_claim

Checks whether revenue_center_code is null on an institutional claim line.

revenue_center_code

missing

Severity 2

medication

days_supply is negativemedication__days_supply_negative

Checks whether days_supply is less than zero in the medication Input Layer Model.

days_supply

invalid

Severity 2

medication

dispensing_date is out of rangemedication__dispensing_date_out_of_range

Checks whether dispensing_date in the medication Input Layer Model is before 2000-01-01 or after the current date.

dispensing_date

invalid

Severity 2

medication

encounter_id not found in encounter tablemedication__encounter_id_not_in_encounter

Checks whether populated encounter_id values in the medication Input Layer Model have a corresponding encounter_id in the encounter Input Layer Model for the same data_source.

encounter_id, data_source

referential

Severity 2

medication

encounter_id, person_id, and patient_id combination not found in encounter tablemedication__encounter_person_patient_pair_not_in_encounter

Checks whether a populated encounter_id exists for the data_source and the populated person_id and patient_id pair exists in the patient Input Layer Model, but the encounter is not assigned to that exact pair in the encounter Input Layer Model.

encounter_id, person_id, patient_id, data_source

referential

Severity 2

medication

ingest_datetime is out of reasonable rangemedication__ingest_datetime_out_of_reasonable_range

Checks whether a populated ingest_datetime in the medication Input Layer Model is before 2000-01-01 or after the current date.

ingest_datetime

invalid

Severity 2

medication

ndc_code is invalidmedication__ndc_code_invalid

Checks whether a populated ndc_code is absent from the selected CodeRx packages terminology after Tuva removes hyphens from both values before comparison.

ndc_code

invalid

Severity 2

medication

patient_id is nullmedication__patient_id_null

Checks whether patient_id is null in the medication Input Layer Model.

patient_id

missing

Severity 2

medication

patient_id not found in patient tablemedication__patient_id_not_in_patient

Checks whether patient_id values in the medication Input Layer Model have a corresponding patient_id in the patient Input Layer Model for the same data_source.

patient_id, data_source

referential

Severity 2

medication

person_id and patient_id pair not found in patient tablemedication__person_patient_pair_not_in_patient

Checks whether populated person_id and patient_id values each exist in the patient Input Layer Model for the same data_source but their exact pair does not.

person_id, patient_id, data_source

referential

Severity 2

medication

person_id is nullmedication__person_id_null

Checks whether person_id is null in the medication Input Layer Model.

person_id

missing

Severity 2

medication

person_id not found in patient tablemedication__person_id_not_in_patient

Checks whether person_id values in the medication Input Layer Model have a corresponding person_id in the patient Input Layer Model for the same data_source.

person_id, data_source

referential

Severity 2

medication

practitioner_id not found in practitioner tablemedication__practitioner_id_not_in_practitioner

Checks whether populated practitioner_id values in the medication Input Layer Model have a corresponding practitioner_id in the practitioner Input Layer Model for the same data_source.

practitioner_id, data_source

referential

Severity 3

medication

prescribing_date is after dispensing_datemedication__prescribing_date_after_dispensing_date

Checks whether prescribing_date is after dispensing_date in the medication Input Layer Model.

dispensing_date, prescribing_date

temporal

Severity 2

medication

prescribing_date is out of rangemedication__prescribing_date_out_of_range

Checks whether prescribing_date in the medication Input Layer Model is before 2000-01-01 or after the current date.

prescribing_date

invalid

Severity 2

medication

quantity is negativemedication__quantity_negative

Checks whether quantity is less than zero in the medication Input Layer Model.

quantity

invalid

Severity 2

medication

source_code is invalidmedication__source_code_invalid

Checks whether a populated source_code is absent from the selected CodeRx packages terminology when source_code_type identifies NDC without regard to letter case. Tuva removes hyphens from both values before comparison. Every other source_code_type, including RxNorm, ATC, and a source-system-specific name, is not applicable to this code-validity test.

source_code_type, source_code

invalid

Severity 2

medication

source_code is nullmedication__source_code_null

Checks whether source_code is null when source_code_type is populated in the medication Input Layer Model.

source_code_type, source_code

missing

Severity 2

medication

source_code_type is null when source_code is presentmedication__source_code_type_null_when_source_code_present

Checks whether source_code_type is null when source_code is populated in the medication Input Layer Model.

source_code_type, source_code

missing

Severity 2

observation

encounter_id not found in encounter tableobservation__encounter_id_not_in_encounter

Checks whether populated encounter_id values in the observation Input Layer Model have a corresponding encounter_id in the encounter Input Layer Model for the same data_source.

encounter_id, data_source

referential

Severity 2

observation

encounter_id, person_id, and patient_id combination not found in encounter tableobservation__encounter_person_patient_pair_not_in_encounter

Checks whether a populated encounter_id exists for the data_source and the populated person_id and patient_id pair exists in the patient Input Layer Model, but the encounter is not assigned to that exact pair in the encounter Input Layer Model.

encounter_id, person_id, patient_id, data_source

referential

Severity 2

observation

ingest_datetime is out of reasonable rangeobservation__ingest_datetime_out_of_reasonable_range

Checks whether a populated ingest_datetime in the observation Input Layer Model is before 2000-01-01 or after the current date.

ingest_datetime

invalid

Severity 2

observation

observation_date is nullobservation__observation_date_null

Checks whether observation_date is null in the observation Input Layer Model.

observation_date

missing

Severity 2

observation

observation_date is out of rangeobservation__observation_date_out_of_range

Checks whether observation_date in the observation Input Layer Model is before 2000-01-01 or after the current date.

observation_date

invalid

Severity 2

observation

observation_type is invalidobservation__observation_type_invalid

Checks whether observation_type is populated in the observation Input Layer Model but not found in Tuva observation type terminology.

observation_type

invalid

Severity 2

observation

patient_id is nullobservation__patient_id_null

Checks whether patient_id is null in the observation Input Layer Model.

patient_id

missing

Severity 2

observation

patient_id not found in patient tableobservation__patient_id_not_in_patient

Checks whether patient_id values in the observation Input Layer Model have a corresponding patient_id in the patient Input Layer Model for the same data_source.

patient_id, data_source

referential

Severity 2

observation

person_id and patient_id pair not found in patient tableobservation__person_patient_pair_not_in_patient

Checks whether populated person_id and patient_id values each exist in the patient Input Layer Model for the same data_source but their exact pair does not.

person_id, patient_id, data_source

referential

Severity 2

observation

person_id is nullobservation__person_id_null

Checks whether person_id is null in the observation Input Layer Model.

person_id

missing

Severity 2

observation

person_id not found in patient tableobservation__person_id_not_in_patient

Checks whether person_id values in the observation Input Layer Model have a corresponding person_id in the patient Input Layer Model for the same data_source.

person_id, data_source

referential

Severity 2

observation

source_code is invalidobservation__source_code_invalid

Checks whether a populated source_code is absent from the corresponding terminology when source_code_type identifies LOINC, SNOMED CT, ICD-10-CM, ICD-9-CM, ICD-10-PCS, or ICD-9-PCS without regard to letter case. Every other source_code_type, including HCPCS and a source-system-specific name, is not applicable to this code-validity test.

source_code_type, source_code

invalid

Severity 2

observation

source_code is nullobservation__source_code_null

Checks whether source_code is null when source_code_type is populated in the observation Input Layer Model.

source_code_type, source_code

missing

Severity 2

observation

source_code_type is null when source_code is presentobservation__source_code_type_null_when_source_code_present

Checks whether source_code_type is null when source_code is populated in the observation Input Layer Model.

source_code_type, source_code

missing

Severity 2

patient

birth_date has multiple values per person_idpatient__multiple_birth_dates_per_person

Checks whether the same person_id and data_source identify records with more than one non-null birth_date in the patient Input Layer Model.

birth_date

consistency

Severity 2

patient

birth_date is after death_datepatient__birth_date_after_death_date

Checks whether birth_date is after death_date in the patient Input Layer Model.

birth_date, death_date

temporal

Severity 2

patient

birth_date is nullpatient__birth_date_null

Checks whether birth_date is null in the patient Input Layer Model.

birth_date

missing

Severity 2

patient

birth_date is out of rangepatient__birth_date_out_of_range

Checks whether birth_date in the patient Input Layer Model is before 1900-01-01 or after the current date.

birth_date

invalid

Severity 2

patient

death_date is out of rangepatient__death_date_out_of_range

Checks whether death_date in the patient Input Layer Model is before 1900-01-01 or after the current date.

death_date

invalid

Severity 2

patient

death_date populated without death_flagpatient__death_date_without_death_flag

Checks whether death_date is populated in the patient Input Layer Model while death_flag is null or 0.

death_date, death_flag

consistency

Severity 3

patient

death_flag indicates death without death_datepatient__death_flag_without_death_date

Checks whether death_flag is 1 in the patient Input Layer Model while death_date is null.

death_date, death_flag

consistency

Severity 3

patient

death_flag is invalidpatient__death_flag_invalid

Checks whether death_flag in the patient Input Layer Model is populated with a value other than 0 or 1.

death_flag

invalid

Severity 3

patient

ethnicity is invalidpatient__ethnicity_invalid

Checks whether ethnicity in the patient Input Layer Model is populated but not found in Tuva ethnicity terminology.

ethnicity

invalid

Severity 3

patient

ingest_datetime is out of reasonable rangepatient__ingest_datetime_out_of_reasonable_range

Checks whether a populated ingest_datetime in the patient Input Layer Model is before 2000-01-01 or after the current date.

ingest_datetime

invalid

Severity 2

patient

race is invalidpatient__race_invalid

Checks whether race in the patient Input Layer Model is populated but not found in Tuva race terminology.

race

invalid

Severity 3

patient

sex has multiple values per person_idpatient__multiple_sexes_per_person

Checks whether the same person_id and data_source identify records with more than one exact non-null sex value in the patient Input Layer Model. Letter-case variants are distinct values.

sex

consistency

Severity 3

patient

sex is invalidpatient__sex_invalid

Checks whether sex in the patient Input Layer Model is populated with a value other than the exact lowercase values male, female, or unknown.

sex

invalid

Severity 3

patient

sex is nullpatient__sex_null

Checks whether sex is null in the patient Input Layer Model.

sex

missing

Severity 3

patient

state is invalidpatient__state_invalid

Checks whether state is populated in the patient Input Layer Model but does not match an ANSI/FIPS state abbreviation, state name, or state code.

state

invalid

Severity 3

patient

zip_code has an invalid formatpatient__zip_code_invalid_format

Checks whether zip_code is populated in the patient Input Layer Model but is not a 5-digit ZIP code, 9-digit ZIP code, or ZIP+4 value.

zip_code

invalid

Severity 3

pharmacy_claim

allowed_amount is less than zeropharmacy_claim__allowed_amount_lt_zero

Checks whether allowed_amount is less than zero on a pharmacy claim line.

allowed_amount

invalid

Severity 2

pharmacy_claim

allowed_amount is nullpharmacy_claim__allowed_amount_null

Checks whether allowed_amount is null on a pharmacy claim line.

allowed_amount

missing

Severity 2

pharmacy_claim

claim line number is not positivepharmacy_claim__claim_line_number_not_positive

Checks whether a populated claim_line_number on a pharmacy claim is zero or negative.

claim_line_number

invalid

Severity 1

pharmacy_claim

days supply is not positivepharmacy_claim__days_supply_not_positive

Checks whether a populated days_supply on a pharmacy claim line is zero or negative.

days_supply

invalid

Severity 2

pharmacy_claim

days supply is nullpharmacy_claim__days_supply_null

Checks whether days_supply is null on a pharmacy claim line.

days_supply

missing

Severity 2

pharmacy_claim

dispensing_date is nullpharmacy_claim__dispensing_date_null

Checks whether dispensing_date is null on a pharmacy claim line.

dispensing_date

missing

Severity 1

pharmacy_claim

dispensing_date is out of reasonable rangepharmacy_claim__dispensing_date_out_of_reasonable_range

Checks whether dispensing_date on a pharmacy claim line is before 2000-01-01 or after the current date.

dispensing_date

invalid

Severity 2

pharmacy_claim

dispensing_provider_npi is invalidpharmacy_claim__dispensing_provider_npi_invalid

Checks whether dispensing_provider_npi is populated but not found in Tuva provider data.

dispensing_provider_npi

invalid

Severity 2

pharmacy_claim

dispensing_provider_npi is nullpharmacy_claim__dispensing_provider_npi_null

Checks whether dispensing_provider_npi is null on a pharmacy claim line.

dispensing_provider_npi

missing

Severity 3

pharmacy_claim

file_date is outside the supported date rangepharmacy_claim__file_date_outside_supported_date_range

Checks whether a populated file_date in the pharmacy_claim Input Layer Model is before 2000-01-01 or after the current date. Structural Data Quality validates the native SQL DATE type; this Logical test does not inspect a serialized string format.

file_date

invalid

Severity 2

pharmacy_claim

in_network_flag is invalidpharmacy_claim__in_network_flag_invalid

Checks whether in_network_flag in the pharmacy_claim Input Layer Model is populated with a value other than 0 or 1.

in_network_flag

invalid

Severity 2

pharmacy_claim

ingest_datetime is out of reasonable rangepharmacy_claim__ingest_datetime_out_of_reasonable_range

Checks whether a populated ingest_datetime in the pharmacy_claim Input Layer Model is before 2000-01-01 or after the current date.

ingest_datetime

invalid

Severity 2

pharmacy_claim

ndc_code is invalidpharmacy_claim__ndc_code_invalid

Checks whether ndc_code is populated but not found in the selected CodeRx packages terminology.

ndc_code

invalid

Severity 2

pharmacy_claim

ndc_code is nullpharmacy_claim__ndc_code_null

Checks whether ndc_code is null on a pharmacy claim line.

ndc_code

missing

Severity 2

pharmacy_claim

no matching eligibility spanpharmacy_claim__no_matching_eligibility_span

Checks whether a pharmacy claim line with a complete person_id, member_id, payer, plan, and data_source identity and populated paid_date has no eligibility span for the same complete identity whose covered calendar months include the paid_date month. Rows whose paid_date is outside the valid range from 2000-01-01 through the current date, outside the member-month spine from 1900-01 through 2100-12, or after tuva_last_run are not applicable. Eligibility coverage is evaluated only through the calendar month containing tuva_last_run: null and the legacy 9999-12-31 alias use that as-of boundary, and a later finite enrollment_end_date is capped to the same boundary.

person_id, member_id, payer, plan, paid_date, data_source

referential

Severity 2

pharmacy_claim

paid_amount is greater than allowed_amountpharmacy_claim__paid_amount_gt_allowed_amount

Checks whether paid_amount is greater than allowed_amount on a pharmacy claim line.

allowed_amount, paid_amount

consistency

Severity 2

pharmacy_claim

paid_amount is less than zeropharmacy_claim__paid_amount_lt_zero

Checks whether paid_amount is less than zero on a pharmacy claim line.

paid_amount

invalid

Severity 2

pharmacy_claim

paid_amount is nullpharmacy_claim__paid_amount_null

Checks whether paid_amount is null on a pharmacy claim line.

paid_amount

missing

Severity 2

pharmacy_claim

paid_date is nullpharmacy_claim__paid_date_null

Checks whether paid_date is null on a pharmacy claim line.

paid_date

missing

Severity 1

pharmacy_claim

paid_date is out of reasonable rangepharmacy_claim__paid_date_out_of_reasonable_range

Checks whether paid_date on a pharmacy claim line is before 2000-01-01 or after the current date.

paid_date

invalid

Severity 2

pharmacy_claim

person_id has multiple values per claimpharmacy_claim__multiple_person_ids_per_claim

Checks whether a pharmacy claim_id is associated with more than one person_id within the same data_source.

person_id

consistency

Severity 1

pharmacy_claim

person_id is nullpharmacy_claim__person_id_null

Checks whether person_id is null on a pharmacy claim line.

person_id

missing

Severity 1

pharmacy_claim

prescribing_provider_npi is invalidpharmacy_claim__prescribing_provider_npi_invalid

Checks whether prescribing_provider_npi is populated but not found in Tuva provider data.

prescribing_provider_npi

invalid

Severity 2

pharmacy_claim

prescribing_provider_npi is nullpharmacy_claim__prescribing_provider_npi_null

Checks whether prescribing_provider_npi is null on a pharmacy claim line.

prescribing_provider_npi

missing

Severity 3

pharmacy_claim

quantity is not positivepharmacy_claim__quantity_not_positive

Checks whether a populated quantity on a pharmacy claim line is zero or negative.

quantity

invalid

Severity 2

pharmacy_claim

quantity is nullpharmacy_claim__quantity_null

Checks whether quantity is null on a pharmacy claim line.

quantity

missing

Severity 2

pharmacy_claim

refills is less than zeropharmacy_claim__refills_lt_zero

Checks whether a populated refills value on a pharmacy claim line is negative.

refills

invalid

Severity 2

practitioner

ingest_datetime is out of reasonable rangepractitioner__ingest_datetime_out_of_reasonable_range

Checks whether a populated ingest_datetime in the practitioner Input Layer Model is before 2000-01-01 or after the current date.

ingest_datetime

invalid

Severity 2

practitioner

NPI is invalidpractitioner__npi_invalid

Checks whether npi is populated in the practitioner Input Layer Model but not found in Tuva provider data.

npi

invalid

Severity 2

practitioner

NPI is not assigned to an individualpractitioner__npi_not_individual

Checks whether npi in the practitioner Input Layer Model is found in Tuva provider data but has an NPPES entity type other than individual.

npi

invalid

Severity 2

procedure

code_system is invalidprocedure__code_system_invalid

Checks whether code_system in the procedure Input Layer Model is populated with a value other than icd-10-pcs, icd-9-pcs, hcpcs, or snomed-ct without regard to letter case.

code_system

invalid

Severity 2

procedure

code_system is nullprocedure__code_system_null

Checks whether code_system is null in the procedure Input Layer Model.

code_system

missing

Severity 2

procedure

encounter_id not found in encounter tableprocedure__encounter_id_not_in_encounter

Checks whether populated encounter_id values in the procedure Input Layer Model have a corresponding encounter_id in the encounter Input Layer Model for the same data_source.

encounter_id, data_source

referential

Severity 2

procedure

encounter_id, person_id, and patient_id combination not found in encounter tableprocedure__encounter_person_patient_pair_not_in_encounter

Checks whether a populated encounter_id exists for the data_source and the populated person_id and patient_id pair exists in the patient Input Layer Model, but the encounter is not assigned to that exact pair in the encounter Input Layer Model.

encounter_id, person_id, patient_id, data_source

referential

Severity 2

procedure

ingest_datetime is out of reasonable rangeprocedure__ingest_datetime_out_of_reasonable_range

Checks whether a populated ingest_datetime in the procedure Input Layer Model is before 2000-01-01 or after the current date.

ingest_datetime

invalid

Severity 2

procedure

patient_id is nullprocedure__patient_id_null

Checks whether patient_id is null in the procedure Input Layer Model.

patient_id

missing

Severity 2

procedure

patient_id not found in patient tableprocedure__patient_id_not_in_patient

Checks whether patient_id values in the procedure Input Layer Model have a corresponding patient_id in the patient Input Layer Model for the same data_source.

patient_id, data_source

referential

Severity 2

procedure

person_id and patient_id pair not found in patient tableprocedure__person_patient_pair_not_in_patient

Checks whether populated person_id and patient_id values each exist in the patient Input Layer Model for the same data_source but their exact pair does not.

person_id, patient_id, data_source

referential

Severity 2

procedure

person_id is nullprocedure__person_id_null

Checks whether person_id is null in the procedure Input Layer Model.

person_id

missing

Severity 2

procedure

person_id not found in patient tableprocedure__person_id_not_in_patient

Checks whether person_id values in the procedure Input Layer Model have a corresponding person_id in the patient Input Layer Model for the same data_source.

person_id, data_source

referential

Severity 2

procedure

practitioner_id not found in practitioner tableprocedure__practitioner_id_not_in_practitioner

Checks whether populated practitioner_id values in the procedure Input Layer Model have a corresponding practitioner_id in the practitioner Input Layer Model for the same data_source.

practitioner_id, data_source

referential

Severity 3

procedure

procedure_date is nullprocedure__procedure_date_null

Checks whether procedure_date is null in the procedure Input Layer Model.

procedure_date

missing

Severity 2

procedure

procedure_date is out of rangeprocedure__procedure_date_out_of_range

Checks whether procedure_date in the procedure Input Layer Model is before 2000-01-01 or after the current date.

procedure_date

invalid

Severity 2

procedure

source_code is invalidprocedure__source_code_invalid

Checks whether a populated source_code is absent from the corresponding terminology when code_system identifies ICD-10-PCS, ICD-9-PCS, or SNOMED CT without regard to letter case. Every other code_system, including HCPCS, is not applicable to this code-validity test.

code_system, source_code

invalid

Severity 2

procedure

source_code is nullprocedure__source_code_null

Checks whether source_code is null in the procedure Input Layer Model.

source_code

missing

Severity 2

provider_attribution

ingest_datetime is out of reasonable rangeprovider_attribution__ingest_datetime_out_of_reasonable_range

Checks whether a populated ingest_datetime in the provider_attribution Input Layer Model is before 2000-01-01 or after the current date.

ingest_datetime

invalid

Severity 2

provider_attribution

year_month is invalid YYYYMM formatprovider_attribution__year_month_invalid_format

Checks whether a populated year_month in the provider_attribution Input Layer Model is an exact six-digit YYYYMM value with a valid month from 01 through 12.

year_month

invalid

Severity 1