Supervised CHW services
Vetted, trained, supervised CHWs from the CHW Academy pipeline. Field supervisors carry visibility into the substrate.
- Provider-reviewed scope
- Field supervisor coverage
- Governed scheduling
Service · CHW field team
CHWs navigating communities, mapped.
Trained, supervised, governed CHW teams extending primary care into the home and community — with a route map, simulated GPS, home-visit checklist, and provider link-in built in. Provider review on every clinically relevant action.
Core services
Five workflows, one governed substrate.
Each service runs on the JoyPartnersOS platform with assignment-aware permissions and audit-emitting actions. CHWs do not sign off clinical determinations; providers retain final clinical authority.
Outreach & engagement
Door-step engagement and trusted-adult care navigation. Reach into communities that primary care alone cannot serve at scale.
- Plan-driven outreach
- Consent capture
- Audit-emitting communications
SDOH screening & education
Structured screening for transportation, food access, housing stability, caregiver network, and health literacy — captured into the plan workspace.
- Plan v3 templates
- Barrier capture taxonomy
- Provider review gate
Referral navigation & follow-up
Closed-loop referrals with partner-side visibility. Closure events emit audit entries. Open-beyond-SLA referrals trigger acknowledgments.
- Partner visibility
- Closure-rate analytics
- SLA acknowledgment
Care plan support & monitoring
Versioned plans with provider-authored goals. CHWs execute care-team tasks; providers see closure and outcomes trends in real time.
- Plan-versioned tasks
- Provider command center
- Outcomes trend lines
Evidence custody & audit
Raw transcripts, audio, and photos stay under controlled custody. PHI-minimized metadata flows downstream. Audit emission is always on.
- Ledger-tagged refs
- PHI-minimization
- Always-on audit
Operating model
Vetted, trained, supervised. Audit-trail by default.
Joy Partners staffs and supervises the field team. Providers retain final clinical authority. JoyPartnersOS is the substrate underneath.
- Recruit & train. CHWs are sourced and trained through the JoyPartnersOS-aligned CHW Academy. Substrate fluency is built in before deployment.
- Assign & scope. Provider Group Demo (or your group) scopes the panel, visit cadence, and clinical guardrails. JoyPartnersOS provisions queues and assignment-aware permissions.
- Operate & capture. CHWs run smart visits, capture barriers, document care navigation. Evidence anchors flow into the plan workspace and audit ledger.
- Loop the provider in. Telehealth broadcast (provider → assigned CHWs) and provider link-in (CHW → provider) keep clinical authority where it belongs. Audit emits on join.
- Close the referral. Network partners see real-time status, closure summaries, and SLA acknowledgment paths. Open-beyond-SLA referrals trigger flags, not silent timeouts.
Substrate boundaries
What CHWs do — and what they don't.
CHWs do
- Run smart visits. Structured field encounters with consent, readiness, barrier capture, plan-task execution.
- Capture evidence. Notes, observations, references — staged for provider review, audit-anchored.
- Coordinate care. Network partners, providers, supervisors — communications emit metadata into the audit ledger.
- Document barriers. Transportation, food access, environmental, caregiver — across the plan workspace.
- Escalate. Provider link-in via telehealth broadcast when clinically relevant.
CHWs do not
- Sign off clinical determinations. Provider review is the only path.
- Generate CPT decisions. CPT candidates are staged for provider sign-off, not auto-billed.
- Write to the commercial / payroll / clinical ledger directly. Workforce-ledger writes only.
- Access PHI beyond their assignment. Default-deny outside assigned panel.
- Act autonomously on clinically relevant signals. Human review gate is always required.
Future geospatial integration
Future production versions may integrate Google Maps Platform capabilities — map rendering, geocoding, route optimization, travel-time estimates, Street View-style context, and aerial / 3D geospatial views. Any production integration would require patient consent, role-based access, audit trails, HIPAA-aligned vendor review, data minimization, and operator-governed configuration. This dev preview uses local synthetic data only and does not call Google APIs.
Compliance-safe disclaimer
Service envelope and intent only. No HIPAA, FDA, SOC2, HITRUST, or reimbursement certification claim. No autonomous clinical, billing, payroll, or legal decisioning. Synthetic identifiers only.