Introducing Vlada Studio. Your healthcare research analyst.Now open.
Book a demo →Home / Tools / Medicare Advantage, Part D, Medicaid
get_county_view
Get County View
What it answers
The whole Medicare Advantage picture of ONE county, over time, in one call: (1) enrollment by parent and product type each September from 2021, with CMS small-cell suppression carried as a floor and a ceiling, and the county's MA penetration where CMS holds it; (2) plan exits for every transition from 2023: continuing, departing, the five Day-One buckets, the true outcome where the crosswalk is held or the calibrated estimate range where not, parents before and parents continuing; (3) the same members' plan design this year against next (total premium, $0 premium share, MOOP, $0 Part D deductible share, D-SNP $0 cost sharing, star), at county grain where held, else the state figures under their own name with a coded note (get_landscape_benefit_change serves twelve metrics at state grain); (4) every plan sold in the county in the plan year with premium, MOOP, deductible and star, the D-SNP fields in their own columns, paged; (5) September members in contracts rated 4+ stars by rating year, with the rating-year to payment-year clock. Every tile is one row per product type with arrays over years or transitions, so the county reads over time in one call.
ARGUMENTS: state (two-letter) and county (the county name as CMS spells it, e.g. 'Cook', 'DuPage'; 'County' may be included or left off; a misspelling is refused naming the nearest CMS spellings), OR county_fips (five digits, e.g. '17031'), OR county_ssa (the five-digit CMS SSA state-county code, e.g. '14140', resolved to its FIPS through the CMS penetration file); year (the plan year for the plan list, default the newest Landscape year held); sections (comma-separated subset of enrollment, exits, benefit_change, plans, stars; default all); detail: the two modes, summary (default, false: the product-type tiles, which fit one answer) and full (true: the tiles plus the parent x product type rows for enrollment and for the newest exits transition, and the plan list itself, paged); limit (rows per detail list per page, default 5, max 200) and offset (default 0), which page every detail list together, so a long page is one section at a time (sections=plans, detail=true, limit=100); include_cost_mmp (default false: industry = every product type but Cost and MMP).
RETURNS value.blocks (one block per section: source, edition, the five clocks, the base, the seconds it took, its caveats, and a status of measured, substituted or unavailable with a code), value.county_by_year, value.enrollment_by_product_type, value.exits_by_product_type, value.benefit_change, value.plans_by_product_type, value.stars_exposure, value.summary; with detail=true also value.enrollment (parent x product type), value.exits (parent x product type, newest transition) and value.plans, each paged by limit and offset.
RULES THE TOOL ENFORCES: the county is resolved by FIPS and the name key the Landscape carries is derived, never typed; the member base is H/R contracts, plans 001-799, September Y, matched to the Y Landscape by plan AND county; stand-alone Part D is never in it; D-SNP is its own product type and is never pooled; suppressed cells are carried as a floor and a ceiling, so every rollup keeps its bounds; parent is CMS's reported parent at each September and a parent's figure is the sum of its members, never a plan count; every section names its clocks.
SOURCE: Vlada analysis of the CMS monthly enrollment by plan and county, the CMS MA state-county penetration file, the CMS MA/Part D Landscape files, the CMS plan crosswalk where held, and the CMS Star Ratings.
Inputs
countycounty_fipscounty_ssadetailinclude_cost_mmplimitoffsetsectionsstateyearCall it
From an agent: connect the Vlada MCP once (one click for Claude, ChatGPT, Cursor, VS Code) and ask in plain English; the agent selects get_county_view when the question fits. From code: the same tool over REST with an API key. The schema endpoint needs no key.
curl -X POST https://api.vladahealth.com/v1/tools/get_county_view \
-H "Authorization: Bearer $VLADA_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'curl https://api.vladahealth.com/v1/tools/get_county_view/schema # the JSON schema, no auth # MCP endpoint (Streamable HTTP): https://mcp.vladahealth.com/mcp
What comes back
Typed rows plus provenance on every answer: the public source file, its vintage, the methodology, and a response_hash you can replay. Prove and replay tools turn any number into a re-runnable receipt. A number the data cannot support comes back as “not in the data”, never as zero.
Sources behind it
- medicare_silver.enrollment_monthly_county
- medicare_silver.ma_state_county_penetration
- medicare_silver.fact_ma_landscape
- medicare_silver.stars_ratings_summary
- medicare_silver.plan_crosswalks_annual
- medicare_semantic.fact_landscape_disposition_v1
- medicare_semantic.fact_landscape_benefits_v1
tables: medicare_silver.enrollment_monthly_county · medicare_silver.ma_state_county_penetration · medicare_silver.fact_ma_landscape · medicare_silver.stars_ratings_summary · medicare_silver.plan_crosswalks_annual
views: medicare_semantic.fact_landscape_disposition_v1 · medicare_semantic.fact_landscape_benefits_v1
Known limits
No gaps recorded for this tool. Absence of a recorded gap is not a claim of complete coverage; the answer itself says what it covers.
As of the 2026-09-30 build of the served surface · machine-readable catalog · the live server may run a different version; the schema endpoint above is authoritative for what is deployed.