Saltar al contenido principal

Plainly es una herramienta gratuita. No es parte de ninguna agencia del gobierno.

Planes de salud de Medicaid en Itasca service area, MN

Condados incluidos

Itasca

Minnesota Department of Human Services Obtenido el 2026-07-17

Los planes aparecen en orden alfabético. Plainly no clasifica los planes.

Itasca County Health and Human Services

Itasca Medical Care (IMCare)

Más sobre este plan

Servicios para miembros: 1-800-843-9536

No hay calificación disponible. Ver calificaciones NCQA

Aún no hay beneficios extra en la lista.

This file covers Minnesota's Families and Children Prepaid Medical Assistance Program (PMAP), the state's core Medicaid managed care program, the same program-scope decision NY.json made when it anchored on the MCAID marker rather than every program variant. Minnesota also runs MinnesotaCare (a separate, related program for people over the Medical Assistance income limit), Minnesota Senior Health Options and Minnesota Senior Care Plus (MSHO/MSC+, for seniors, mostly dual Medicare/Medicaid eligible), and Special Needs BasicCare (SNBC); each of those programs is published by DHS as its own county-by-county map (DHS-4326, DHS-4840, DHS-5218) with a roster that can differ from PMAP's, and none of those three is represented in this file. enrollment.portal_url, enrollment.portal_name, and enrollment.phone are quote-gate verified against a captured Minnesota Department of Human Services page (mn.gov/dhs/health-plan-selection/) describing the state's Annual Health Plan Selection (AHPS) process. All 9 service area roster facts (areas.<slug>.plans) are quote-gate verified against a captured snapshot of DHS's own DHS-4324-ENG map, 'Families and Children Prepaid Medical Assistance Program (PMAP) Health Plan Choices by County, Effective January 1, 2026 to December 31, 2026' (a PDF hosted on DHS's edocs.dhs.state.mn.us document server), which lists every one of Minnesota's 87 counties on a single page as plain text (county name, choice count, and the exact plan names), not as a colorized map alone; unlike NY's per-plan-then-per-county source, this DHS source is already organized per county with every plan for that county listed together, so no cross-referencing across multiple plan-specific tables was needed to build each area's roster value; the two DHS pages I tried first for a machine-readable county table (mn.gov/dhs/partners-and-providers/policies-procedures/minnesota-health-care-programs/provider/mcos/ and www.dhs.state.mn.us's idcplg-served Managed Care Manual pages) are behind an automated bot challenge (perfdrive/Radware) that blocked every fetch attempt, so DHS-4324-ENG's PDF (fetched directly from edocs.dhs.state.mn.us, a different, unblocked DHS subdomain) is the source actually used; this is the secondary-format situation the authoring rules anticipated (an interactive/graphical presentation with a companion text-bearing document DHS also publishes), except this particular DHS document already had full text embedded per-county underneath its map graphic, not merely a legend. One fetch mechanics note for a human reviewer: DHS-4324-ENG's URL has no '.pdf' suffix even though the server returns it as application/pdf, and scripts/fetch-plan-snapshots.ts's isPdf check is a URL-suffix test, so the standard `pnpm plans:fetch-snapshots -- --only MN` run captured this source as if it were HTML and produced unusable binary garbage; I fetched the same URL again and ran it through the identical normalizePdfText pipeline the script itself uses for '.pdf' URLs (src/lib/source-monitor/normalizers.ts, no code in that shared script or the checked-in normalizer was edited), then wrote the resulting text to the same seed/plans/snapshots/MN/mn-dhs-pmap-plans-by-county.txt path and recomputed its content_sha256 by hand; that sha256 in this file matches the .txt file actually on disk byte for byte, so check:plans' snapshot-integrity and quote-gate checks both verify against the real captured text, but scripts/fetch-plan-snapshots.ts itself would need a content-type-aware (not just URL-suffix) PDF check to reproduce this capture automatically for MN next time, worth flagging to the foundation engineer. I compressed Minnesota's 87 counties into 9 roster-distinct service areas by grouping every county with an IDENTICAL PMAP plan combination together, cross-checked twice against the actual extracted text (a first pass read a rendered image of the PDF and mis-transcribed three counties; rereading the real extracted snapshot text caught and fixed Freeborn, Murray, and St Louis before finalizing, which is exactly why this workflow insists on quoting the captured file rather than a visual impression of the source) so all 87 counties are accounted for exactly once across the 9 areas and every area's plan_ids resolve to a real plans[] entry: Blue Plus + UCare (25 counties), Blue Plus + Medica (17 counties), PrimeWest Health alone (24 counties, the county-based purchasing plan serving the largest single-choice footprint), South Country Health Alliance alone (7 counties), Itasca Medical Care alone (1 county, Itasca, the county it is named for and the only county it serves), Blue Plus + HealthPartners + Medica (5 counties), Blue Plus + Medica + UCare (2 counties), Blue Plus + HealthPartners + Medica + UCare (5 counties), and Blue Plus + HealthPartners + Hennepin Health + Medica + UCare (1 county, Hennepin, the only county Hennepin Health serves). The source map's own legend renders PrimeWest Health as 'PrimeWest' (no 'Health') on five of its 24 counties (Jackson, Kandiyohi, Lac qui Parle, Lincoln, Lyon) purely due to map label spacing; this file treats those as the same PrimeWest Health entity the legend defines ('PW = PrimeWest Health'), matching every other county's fuller label. The source map marks UCare with a footnote symbol on every county meaning 'not accepting new enrollments'; UCare is included in this file exactly as the state source lists it (a currently operating MCO with existing PMAP members) with that closed-enrollment status documented in its own quality.note, plus the additional context (verified on UCare's and Medica's own sites, informal citation) that UCare Minnesota is winding down under state regulatory supervision with Medica assuming UCare's 2026 Medicaid plans effective January 1, 2026 -- a live transition worth a human reviewer's attention before this file is marked verified. Minnesota Health Care Programs plan selection is run directly by DHS itself, not by a separate statewide enrollment broker the way New York, Florida, or Texas each have one; DHS's own Annual Health Plan Selection page names no broker entity and instead describes a mail-in form and a DHS phone line, so enrollment.broker_name uses DHS's own program name, 'Minnesota Health Care Programs,' rather than inventing a broker that does not exist. That same DHS source describes an annual selection window tied to a fixed calendar deadline (not a fixed number of days after enrollment the way New York's 90-day figure works), so enrollment.choice_window_days stays null rather than forcing a mismatched figure; no not_found fact was added for it since the schema does not require one for an optional field with no comparable source figure. Per-plan member_phone, provider_directory_url, and formulary_url for all 8 plans were independently checked live on each plan's own official Minnesota Health Care Programs / Medicaid page but are not yet cited by a quote-gated fact, the same standing as TX.json/CA.json/NY.json today. Extra benefits are omitted entirely for Itasca Medical Care and PrimeWest Health: IMCare's own site only describes supplemental benefits for its senior (MSHO) product, not Families and Children PMAP, and PrimeWest Health's dedicated extra-benefits page did not return readable content (a JavaScript-rendered shell), so neither plan has a confidently source-backed PMAP-specific extra benefit to report; the other 6 plans' extra_benefits were verified live on each plan's own site. State as a whole stays unverified pending per-plan field citation and the UCare/Medica transition review noted above.

Cómo inscribirse

Fuente: Minnesota Department of Human Services, obtenido el 2026-07-17

Plainly muestra cada plan de salud en su condado. Ningún plan de salud le paga a Plainly. Plainly no gana nada por inscripciones, clics o referencias. Plainly nunca clasifica los planes. Plainly no es el consejero oficial de su estado. Para ayuda oficial gratis, llame al agente de inscripción de su estado o al 211.

Plainly no es un sitio web del gobierno.

Verificado por última vez el 2026-07-17