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.
Provider A, MD
AcceptingProvider B, DO
AcceptingProvider C, MD
01
The directory is where members judge whether your network is real. If they can't quickly find a doctor who speaks their language, takes the plan, and is accepting patients, they call your service line — or they leave at renewal. A fast, accurate search is retention and CMS accuracy in the same surface.
02
Members don't browse a directory; they look for the doctor who speaks their language, takes their plan, and is taking new patients today. The default view sorts by what most members care about — distance and accepting-new-patients — and the filters surface what changes the answer: specialty, language, gender, board certifications.
03
Every provider is geocoded to lat/lng on ingest. Searches use MongoDB 2dsphere indexes for true geographic radius, not bounding boxes. Default radius is 30 miles from a member's ZIP, configurable per plan. Distance-sorted by default; you can override the sort with anything you want.
04
When a plan refreshes its provider roster, the new providers come in tagged with a UUID batch ID. The application reads from the previous batch until the new one is fully validated. Then we swap pointers and delete the old batch. Members never see a half-loaded directory.
05
Each customer's site lives on its own subdomain (e.g. providersearch.{your-plan}.com). Brand color, logo, language pack, module toggles — all configured in the workspace, applied at request time. There is no shared chrome or InsureLytix branding inside the member experience.
Ready when you are
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.
