Regions

Create the regions your team is organized into, then link each CL rep (and Regional Leader) to one from the Users tab. Region referral totals below are summed automatically from their linked CL reps — nothing to fill in for a region directly.

Monthly referral goals. Toggle the year to build out future months ahead of time — these are illustrative starting numbers, not real Chrysalis Health targets.

By region — derived from CL rep goals, read-only

By CL Rep

Each CL rep covers specific counties, so set the goal at that level and it rolls up into their linked region automatically.

Reassigning a rep's counties here doesn't move their existing accounts — that's the bulk reassign tool in Data Tools, or edit a single account directly.

Priority specialties by county

Specialty alone doesn't establish referral potential — a specialty that's a strong prospect in one county can have limited value in another. Flag which specialties matter most in each county here; accounts tagged with a priority specialty for their own county get a small boost in the due-list ranking on the Dashboard and Weekly Route.

Duplicate accounts

Scans every account for likely duplicates — same name and city/county, or the same street address. Pick which record to keep in each group; visits, tasks, referrals, documents, contacts, and route stops move over to it, and it's backfilled with anything it's missing from the ones merged in.

Export data

Downloads a snapshot of everything currently in this prototype. The CSV exports work here and from a hosted preview link; the combined .xlsx workbook needs its spreadsheet library, which only loads when this file is opened directly.

Bulk reassign accounts

Move a batch of accounts to a different CL rep at once — for when someone leaves, or you're redrawing territories.

Import referral counts

A manual stand-in for automatic Power BI sync (see Integrations for why this app can't pull that in on its own yet). Export referral counts from Power BI as a CSV with the account name, month, and count, and bring them in here — matches by exact account name, so make sure names line up with what's in Accounts.

EHR Connection

Referral Lookup searches a local copy of your EHR's intake/referral records, kept in sync by whatever POSTs to the webhook below — a Zapier automation, or an HL7 interface engine's (Mirth, Rhapsody, etc.) outbound HTTP step. This app doesn't speak raw HL7v2 itself; whatever sends data here needs to translate it to the plain JSON shape documented below first.

{
  "externalId": "12345",
  "firstName": "Jordan",
  "lastName": "Rivera",
  "dateOfBirth": "1990-04-12",
  "status": "Active in Treatment",
  "notes": "Intake completed 8/1. Assigned to outpatient program.",
  "sourceSystem": "Zapier"
}

Where each connection to the outside world stands

The ones marked "Built and working" are live right now — the panels further down this page are where you turn each one on, and nobody needs code or server access for any of it.

Microsoft 365 (Outlook Calendar, Email & Sign-in)

This is the one setup step that genuinely can't happen inside this app: Microsoft doesn't offer an API for registering an app in your tenant. Your Microsoft 365 admin does that once in the Entra admin center, and pastes the three values it gives back into the fields below. From that moment on, every rep connects their own account from their own Security screen — nobody needs code or server access for that part, ever, including you.

Teams notifications

Posts to a Teams channel when a new follow-up task is created, and (on a schedule you control) a summary of overdue accounts. This uses a Teams Incoming Webhook, not the Microsoft app above — a Team owner adds that connector from inside Teams itself (⋯ on a channel → Connectors → Incoming Webhook) and gives it a name/icon; paste the URL it generates below.

Zapier / Power BI referral count sync

As referral counts show up in your Power BI reports, a Zap (or a scheduled Power Automate flow) can POST them here directly instead of anyone re-typing them — same webhook pattern as EHR Connection above, with its own independent secret.

{
  "facilityId": "fac12",
  "date": "2026-08-01",
  "insuranceType": "Medicaid",
  "source": "Power BI sync",
  "count": 4
}

Backup & version — v

Everything you enter here — accounts, users, regions, referral budgets, marketing materials, referral lookup records — saves to this app's own database on your server as you go, shared by everyone on the team from any device, not just this browser. Updating the app to a newer version later doesn't touch that database at all (see your README), so there's nothing you need to do day-to-day. Use the backup below before a big change, to move data to a different server, or just for a safety copy on a schedule.