The platform

The complete provider-directory platform for MA plans.

Member search, the FHIR directory API CMS requires, and the analytics that prove your network is adequate — white-labeled to your plan and running on one shared set of data, so nothing drifts out of sync.

Admin dashboard

Twelve executive views, one source of data.

Everything leadership needs to see the network at a glance — health by county, coverage by specialty, where supply meets demand and where it doesn't, plus formulary and data-quality views. It's the same data that produces your CMS adequacy filing, so the story you tell the board and the one you file with CMS agree.

  • Network health snapshot, drillable to county
  • Specialty coverage matrix and geographic heatmaps
  • Disease prevalence vs. supply, formulary analytics, data-quality scorecards
  • Per-customer brand color, logo, and language pack

Network gap analytics

The numbers that survive the audit.

Coverage scored for every county and specialty, weighted by how Medicare patients actually use care and counted against the 65-plus population. The same scores that drive your executive dashboard export as the network-adequacy file you submit to CMS — one set of numbers, two destinations.

  • Adequate ≤ 10 patients/provider, moderate ≤ 20, critical above — pre-computed, instant render
  • Care-pathway weighting: 80% of diabetics see a PCP, not an endocrinologist
  • Medicare-adjusted population (CDC PLACES + Census ACS 65+) — not all-age inflation
  • HSD table export ready for HPMS upload

FHIR Plan-Net API

CMS-0057-F, the morning the rule lands.

A DaVinci PDex Plan-Net (R4) implementation conformant to the seven required resources, with Bulk Data Export ($export), SMART Backend Services authentication, and a Sunfire-compatible feed for plans not yet on FHIR — so members keep finding care while the plan migrates.

  • Practitioner, PractitionerRole, Organization, Location, HealthcareService, InsurancePlan, Endpoint
  • $export with NDJSON streaming, async polling, signed URLs
  • SMART Backend Services: JWT bearer auth, CapabilityStatement, .well-known/smart-configuration
  • Sunfire-compatible feed for legacy plans, with FHIR cutover staged behind a flag

Provider search

The directory members actually use.

A faceted, geo-aware search built for the way Medicare members shop for care — by specialty, language, accepting-new-patients, distance, and certifications. White-labeled per plan and rendered on the plan's own subdomain.

  • Faceted sidebar: specialty, language, gender, certifications, accepting new patients
  • 30-mile radius from ZIP, MongoDB 2dsphere geo-indexed, distance-sorted
  • Autocomplete, configurable pagination, EN/ES localization
  • Atomic refresh: UUID-tagged batch upload, swap-then-delete — zero downtime

Facility search

Hospitals, clinics, urgent care — all on one map.

Same UX pattern as provider search, with services-offered filters, accreditations, minimum-rating, and provider-to-facility cross-reference so a member who picks a doctor sees the hospital they admit at.

  • Filters: services offered, accreditations, minimum rating, distance
  • Pre-computed Leaflet density maps for instant render
  • Provider-to-facility cross-reference works across modules
  • Auto-geocoded via 12-hour Google Maps cron

Pharmacy search

Distance, hours, and inline booking.

Geocoded distance filtering, hours of operation, and inline appointment-booking hooks for partner integrations. Same context provider, same SidebarItems pattern as the rest of the suite.

  • Distance filter, auto-geocoded via 12-hour Google Maps cron
  • Hours, accepting-walk-ins, services, languages
  • Inline appointment-booking hooks for partner integrations
  • Consistent UX with facility module — no member learning curve

Formulary & drug search

Drug → tier → covered provider, in one cross-reference.

Pre-seeded with the CMS Federal Reference Formulary and overlay-able with plan-specific custom formularies via AI-validated CSV upload. Members see drug coverage, tier, prior-auth, and the specialists qualified to prescribe it.

  • Coverage matching: drug → formulary tier → covered-provider eligibility cross-reference
  • Pre-seeded CMS Federal Reference Formulary (FRF)
  • Plan-specific formularies via GPT-4o-validated CSV upload
  • Tier display, prior-auth indicators, step-therapy notices

Ready when you are

Bring this platform to your plan.

If your provider data is ready, a new white-labeled tenant goes live in about a week. Compliance certification runs alongside it, not as a later phase.