For counties and agencies
NavHub is the case management platform behind the Manatee Dementia Public Safety and Navigation Hub. It is built for one funded outcome — reducing avoidable emergency-system use — and it is ready to run in a second county.
1
County live today — Manatee, Florida
300
Families the Manatee grant is funded to serve in year one
8
Weighted risk domains, tuned per county without a release
72h
Escalation clock, scanned by a scheduled job rather than a person
The problem it was built for
Families with no plan and no guidance go to the emergency room. It clogs the ER for everyone, and the family leaves with nothing that lasts.
A referral arrives from an ER, a first responder or the family themselves, and the same day it becomes a case with an owner and a clock — rather than a voicemail nobody returns.
A 100-point, eight-domain weighted model produces a score, a risk code, and a written human reason stored alongside it. Thresholds are configuration, so they are retuned without a release.
Weighted matching returns up to three providers, and the referral is tracked through the call to the outcome. The Hub stays the intermediary — families are never handed a list of websites.
Reporting at 3, 6 and 12 months, built around what the funding is judged on rather than around what happens to be easy to count.
Why a second county is not a rebuild
Grant money is county-restricted. That was a legal requirement on day one, so it is enforced in the data layer rather than by screens that hide buttons.
A navigator in one county cannot see another county’s data. Same codebase, separate data, and continuous integration fails the build if an isolation test regresses.
Weights, bands, override conditions, escalation hours and the keyword list that triggers an emergency escalation are all per-county configuration.
Three role tiers out of the box — secretary, navigator and manager. A secretary can take demographics but cannot perform intake, and that is a guard, not a hidden button.
Every read of a client record is logged: who, when, from which screen. Retention is enforced by a scheduled purge, not by policy. No Social Security numbers, no Medicare numbers, no medical-record uploads — the schema has nowhere to put them.
Starting up
This is the part most platform pitches skip, and it is the part that decides whether your first six months are wasted.
A county begins operating before any platform is live. The interim intake form is designed against the NavHub schema from the start, so going live is a mapping rather than a reconciliation project.
The cases collected during the interim period are imported in one migration. Your navigator signs in on day one and their history is simply there.
New county staff are usually not technically confident. The intake and assessment flows are wizards for that reason.
Straight answers
Asked and answered before you ask.
No 911 or CAD integration, no Area Agency on Aging, no Medicaid. Completion of the state TIFF registry is recorded as a checkbox, because that registry has no integration to offer.
Deliberately excluded. The navigator makes the call and reports back — the Hub stays the intermediary rather than becoming a directory.
Designed, not built. AI today does two narrow things: ordering the navigator’s morning priority list, and flagging emergency-room keywords in inbound family messages. It is never given a name, an address, or anything a family wrote.
A later phase. First responders have bracelet lookup today; ER techs and doctors do not have accounts yet.
NavHub is built by InformedCare360. If you already know their work in assisted living and home care, this is the same team and the same compliance posture.
