Service · turnkey
Joy Partners CHW Field Team
Vetted, supervised CHWs operating on the governed substrate. Provider review on every clinically relevant action.
Governed healthcare operations substrate
CHW-powered, provider-governed care at home.
JoyPartnersOS is the substrate underneath community health workers, home-based primary care, telehealth, referral networks, and ACO programs. Provider review on every clinically relevant action. Four-ledger separation by default. Synthetic-first prototype today.
Built for
- Primary care providers
- Health systems
- ACOs & VBC partners
- Referral networks
- CHW organizations
- Strategic partners & investors
Two ways to deploy
Pick the operating model that fits your group.
Provider groups can deploy a turnkey CHW field team with JoyPartnersOS configured together, or use JoyPartnersOS as a software substrate underneath their existing care team. Software + services compound.
Software · platform
JoyPartnersOS Platform
The substrate: operations inbox, smart visit, telehealth broadcast, provider command center, evidence ledger, audit history, PromptOps governance.
Bundle · house-call
House Call Expansion
Primary care extends into the home. Joy Partners supplies the CHW field operation. JoyPartnersOS supplies the substrate. Configured together.
Bundle · BYO care team
Bring Your Own Care Team
For provider groups that already have a CHW or in-home care team. JoyPartnersOS becomes the substrate underneath, software-only deployment.
Substrate thesis
Whoever owns the workflow graph owns the safe execution surface.
Home-based and CHW-powered care doesn't fail at the clinical model. It fails at the field operation, the evidence-custody chain, the provider oversight loop, and the ledger separation between clinical, commercial, workforce, and audit. JoyPartnersOS is the substrate underneath every one of those — so providers can extend reach without losing control.
What the substrate guarantees
- Controlled states + permissions. Every action passes through identity, permission, assignment-aware access, state precondition, audit emission, and human review.
- Evidence custody. Raw transcripts & audio stay under custody. PHI-minimized metadata flows downstream.
- Ledger separation. Clinical / CPT, Commercial / Provider Invoice, Workforce / Payroll, Platform / Auth / Audit. Default-deny across ledgers.
- PromptOps + AgentOps. Documentation-first governance sequences every non-trivial change. AI acts inside the workflow graph, never on top of it.
What the substrate refuses
- Autonomous clinical decisioning. Provider review is the only path.
- Cross-ledger writes. Clinical surfaces do not create commercial or workforce records.
- Raw PHI flowing downstream. Metadata-only by default.
- Super-admin login bypass. Explicitly prohibited. Safe pattern is normal-auth + dev-only audited impersonation.
Dev preview surfaces
Walk four simulated roles end-to-end.
The dev prototype includes four simulated portals tied to the governance roles defined in the substrate: Provider Command Center, CHW Field Workflow, Referral Partner Portal, and Super Admin Dev Console. All synthetic. No real authentication. No PHI.
Provider
CHW
Referral partner
Super dev admin
Provider Command Center
Operational dashboard for primary care: panel, review queue, telehealth today, field visits & routing map, outcomes trends, care-gap closure.
portal-provider.html
CHW Field Workflow
Field-team workspace: today's visits, route map, SDOH checklist, smart visit composer, barrier capture, provider escalation, time log.
portal-chw.html
Referral Partner Portal
Network partner workspace: active and in-progress referrals, journey timeline, closure analytics, message care team, SLA acknowledgment.
portal-referral.html
Super Admin Dev Console
Governance console: tenants, role & permission map, ledger separation, PromptOps gate trail, audited impersonation (dev-only).
portal-admin.html
CHW field operations
A field team a provider can actually oversee.
Smart visits, telehealth check-ins, barrier documentation, care coordination, referral closure, and consent capture flow into the same operations inbox the provider reviews. AI assists; provider reviews. Every clinically relevant action lands through a human review gate.
| Client | Visit type | Assigned CHW | Status | Ledger |
|---|---|---|---|---|
| Client A-1042 | Smart visit | CHW Team Member 03 | Pending review | Clinical / CPT |
| Client A-1051 | Home assessment | CHW Team Member 07 | Provider review | Clinical / CPT |
| Client A-1068 | Care navigation | CHW Team Member 02 | Approved | Clinical / CPT |
| Client A-1073 | Barrier documentation | CHW Team Member 05 | Consent gap | Platform / Auth / Audit |
Prototype data only — no live PHI, no real client or staff identifiers.
Telehealth-enabled care
Provider link-in that respects custody.
Telehealth Broadcast
Provider-led broadcast for care teams
Push guidance, protocols, or alerts to assigned CHWs under permissioned, audit-emitting delivery.
Telehealth
Provider loop-in for field visits
CHW-initiated telehealth brings a provider into the visit on demand. PHI custody stays inside the platform.
Smart Visit
Structured CHW visit workflow
Consent, readiness, barrier capture, follow-up tasks. AI-assisted, human-reviewed, evidence-supported.
Strategic partners & investors
Software + services. Mission-driven. Acquisition-ready by design.
Concept Factory Labs is operator-builder-led. JoyPartnersOS pairs platform licensing with a supervised CHW field-team service. The combined motion compounds. The governance posture makes the company straightforward to evaluate and absorb.
Compliance-safe disclaimer
- This website is informational. It does not constitute medical, legal, billing, regulatory, or financial advice. It is not an offer to sell securities or a solicitation of an offer to buy securities.
- The substrate is under active development. Nothing on this page is a claim of live production deployment, regulatory clearance, certification (HIPAA, FDA, SOC2, HITRUST, or otherwise), or guaranteed reimbursement.
- No PHI is collected, displayed, or stored by this website. Identifiers shown in product previews are synthetic placeholders only.
- No production endpoints are reachable from this surface. No backend wiring, no API calls, no analytics, no third-party widgets, no embedded forms, no external scripts.
- The dev-preview portals at /login are non-functional simulations. No real authentication, no real session, no real data writes.
- "Super admin bypasses login auth" is explicitly prohibited. The safe pattern is super_dev_admin authenticates normally then uses a dev-only audited impersonation control under a separately authorized non-production gate.
Next step
Talk with the team at Concept Factory Labs.
Provider group, CHW organization, referral partner, payer / ACO, strategic partner, or investor — if your work touches community- anchored care, we'd like to hear from you.