PBP supplemental other (cleaned view)

What it is

1. 1A Medicare Advantage Plan Benefit Package (PBP) semantic view exposing the "other / catch-all supplemental" benefit (CMS PBP Section B-20) per MA plan per CMS data snapshot.
2. 2It is meant to tell you, for each plan offering, whether an "other supplemental" benefit is offered and a few cost-sharing indicator flags (auth required, has-copay/coinsurance/deductible/max-OOP).
3. 3In its current build it is a near-empty SCAFFOLD: the actual dollar/percent cost-share and benefit-amount columns are hardcoded NULL in the view definition, and only 3 contracts / 88 plan-snapshots are materialized.

Grain

How to read it

1. 1To list MA plans that OFFER an 'other supplemental' (B-20) benefit in the latest 2026 snapshot and whether each requires prior auth or carries a copay/coinsurance: SELECT contract_id, plan_id, segment_id, auth_required, has_copay, has_coinsurance, has_max_enrollee_oop FROM medicare_semantic.vw_pbp_supplemental_other WHERE report_year=2026 AND quarter=1.
2. 2This answers 'which of these plans offer the catch-all supplemental benefit and what cost-share types apply' — but for the actual copay/coinsurance AMOUNTS you must join to medicare_silver.pbp_section_b20 on (contract_id, plan_id, segment_id, report_year, quarter), since the amount columns in this view are hardcoded null.

Traps

1. 1This view is a near-empty SCAFFOLD, not a populated benefit table. ~30 of 47 columns are hardcoded CAST(null AS ...) in the view DDL — including EVERY cost-sharing/benefit-amount column (copay_amount, coinsurance_pct, benefit_amount*, limit_*, max_oop_applies, referral_required, normalization_*). They are structurally null regardless of the underlying CMS data. The real dollar/percent values DO exist in medicare_silver.pbp_section_b20 (pbp_b20_b_copay_max, pbp_b20_coins_mc_pct, etc.) and must be joined from there. Do NOT report any rates/amounts from this view.
2. 2has_copay / has_coinsurance / has_max_enrollee_oop can be TRUE while the corresponding amount column is NULL. The 2 'has_*'=true rows (H5264 002 & 005, 2026) still have copay_amount=null and coinsurance_pct=null. The has_* flags only tell you the benefit HAS that cost-share type (decoded from CMS Y/N indicators); they do not give the value.
3. 3No is_current / snapshot-dedup column. The SAME plan repeats once per snapshot — e.g. H1651 plan 001 appears 5 times (2024 Q1/Q3/Q4, 2025, 2026). To avoid multi-counting you MUST filter to a single (report_year, quarter), or pick the latest per plan yourself. quarter is the CMS publication quarter, not a benefit period.
4. 4Tiny / partial materialization. Only 3 contracts and 88 plan-snapshots are present, vs ~1,972 contracts in sibling views (vw_pbp_dental/vision/dme/otc). This reflects two things: (a) PBP Section B-20 is genuinely sparse (silver source = 463 rows / 7 contracts) because most plans don't file an 'other/catch-all' supplemental benefit, and (b) the view is filtered to report_year>=2024 and only a few contracts are built. Do not treat this as MA-wide coverage of supplemental benefits.
5. 5Several columns that look informative are constants and carry no signal: benefit_category='supplemental_other', network_type='in_network', offered_status='offered', numeric_amount_observability='offered_without_numeric_amounts', null_amount_reason='unknown_requires_crosswalk', confidence_tier='source_faithful', consumer_document_reconciliation_status='not_checked', supplemental_other_sub_benefit='other_supplemental', source_pbp_section='B20', cost_share_attestation_text='1' — all single-valued across every row. Also 'benefit_group_count' is mislabeled (it is the raw pbp_b20_bendesc_grp_num group-number string and varies by SNAPSHOT, not by plan), and 'version' is a CMS record version that is plan-specific and FD-determined — it is NOT part of the grain despite the profiler testing it.
6. 6limit_period_code and benefit_amount_period_code (which the profiler tried as grain keys) are 100% null here — they are not keys and were red herrings. The minimal verified grain is just (contract_id, plan_id, segment_id, report_year, quarter).

Columns (50)

Query it

describe_data_source(source_fqn="medicare_semantic.vw_pbp_supplemental_other")     # the card, live
query_substrate(sql="SELECT * FROM medicare_semantic.vw_pbp_supplemental_other WHERE contract_id = '<value>' AND plan_id = '<value>' AND segment_id = '<value>' AND report_year = '<value>' AND quarter = '<value>' LIMIT 100")