Skip to main content

input_layer__eligibility

Enrollment spans as received from the source, before date normalization and de-duplication. Overlapping and duplicated spans are common here and are resolved in the normalized layer.

At a glance​

Schemadax_input_layer
Tableinput_layer__eligibility
LayerInput Layer
Object typeview
Columns47
Grainperson_id, member_id, enrollment_start_date, payer, plan, data_source
Tagsinput_layer

Columns​

ColumnTypeKeyConstraintsDescription
person_idvarcharPK——
member_idvarcharPK——
subscriber_idvarchar——
subscriber_relationvarchar——
enrollment_start_datedatePK——
enrollment_end_datedate——
payervarcharPK——
payer_typevarchar——
planvarcharPK——
first_namevarchar——
middle_namevarchar——
last_namevarchar——
name_suffixvarchar——
social_security_numbervarchar——
addressvarchar——
cityvarchar——
statevarchar——
zip_codevarchar——
phonevarchar——
emailvarchar——
ethnicityvarchar——
sexvarchar——
racevarchar——
birth_datedate——
death_datedate——
death_flaginteger——
original_reason_entitlement_codevarchar——
dual_status_codevarchar——
medicare_status_codevarchar——
enrollment_statusvarchar——
hospice_flaginteger——
institutional_snp_flaginteger——
medicaid_indicatorinteger——
long_term_institutional_flaginteger——
part_d_raf_typevarchar——
low_income_subsidy_indicatorinteger——
metal_levelvarchar——
csr_indicatorinteger——
enrollment_duration_monthsinteger——
esrd_statusinteger——
transplant_duration_monthsinteger——
group_idvarchar——
group_namevarchar——
file_namevarchar——
file_datedate——
ingest_datetimetimestamp——
data_sourcevarcharPK——

Querying​

select *
from dax_input_layer.input_layer__eligibility
limit 100;