Platform license
Practice team
The FQHC’s existing navigators use the workspace, assignments, escalation, and evidence flow.
Navigator partner experience
Extend navigator reach without losing the line of responsibility.
See how an FQHC, its navigators, and a community or workforce partner can run one coordinated operation—while the practice keeps clinical, coding, and claims authority.
- No account required
- Synthetic data only
- No patient access for partner leaders
Practice-controlled
One workflow · three views
1
Navigator
Assigned patients, ranked actions, and visible work authorization.
2
FQHC
Clinical escalation, quality review, and final release authority.
3
Partner
Approved aggregate outcomes and shared operational exceptions.
Interactive synthetic workspace
Follow the same work through three accountable views.
Switch roles to see how a navigator acts, how the FQHC supervises, and what a community or workforce partner can measure. The example is synthetic and does not grant access to the live application.
Kept Count partner scenario
Illustrative workflow · synthetic records
12
Patient actions due
3
Partner follow-ups
1
Escalation tracking
Start here
Next safe actions
- AROpen next action
Amelia R.
Care dueMonthly care-plan follow-up
Priority 1 · owner: Maya, navigator
- RMReview handoff
Robert M.
Partner dueTransportation referral follow-through
Priority 2 · owner: Maya, navigator
- JBTrack escalation
Joyce B.
SupervisorMedication question routed by navigator
Priority 3 · owner: Maya, navigator
One platform · flexible staffing
Keep the care model. Configure who supplies the capacity.
Kept Count does not require an FQHC to replace its team or hand away authority. The operating plan records who employs each navigator, where they may work, what they may do, and when the practice must take over.
Managed operations
IHA-supported capacity
IHA supplies trained navigators inside the practice-approved scope and supervision model.
Joint operating model
Partner or blended team
A community or workforce partner contributes navigators while access remains assignment-bound and practice-controlled.
Access follows responsibility
The partnership is visible without blurring authority.
Partner affiliation alone never opens patient records. Patient work requires a current assignment; external leadership reporting is a separate, aggregate-only access path.
This demo shows the intended operating model. Production activation still requires approved agreements, security review, configured access, training, and practice sign-off.
Patient work
- Navigator
- Assigned navigator
- FQHC
- Practice supervisor
- Partner leader
- Aggregate only
Clinical decisions
- Navigator
- Escalate
- FQHC
- Practice retains
- Partner leader
- No access
Coding and claims
- Navigator
- No authority
- FQHC
- Practice and RCM
- Partner leader
- No access
Program performance
- Navigator
- Own queue
- FQHC
- Practice detail
- Partner leader
- Approved aggregates
| Responsibility | Navigator | FQHC | Partner leader |
|---|---|---|---|
| Patient work | Assigned navigator | Practice supervisor | Aggregate only |
| Clinical decisions | Escalate | Practice retains | No access |
| Coding and claims | No authority | Practice and RCM | No access |
| Program performance | Own queue | Practice detail | Approved aggregates |
Build the real operating brief
Map your navigators, FQHC handoffs, funding constraints, and proof requirements.
We will turn the partnership idea into a bounded workflow before anyone receives production access or handles patient information.