Prototype Dev preview · no production data · simulated portals for review only.  ·  Open simulated portals →

Platform · operations substrate

The operational command center for home-based and CHW-powered care.

JoyPartnersOS is the governed substrate underneath provider review, CHW field work, telehealth, evidence capture, and audit trails. It keeps the workflow graph closed, the ledgers separate, and every clinically relevant action human-reviewed before it lands.

Request a platform walkthrough Open the dev preview →

Static-first prototype No live PHI Four-ledger separation

Capabilities

Eight modules. One governance posture.

Each module is permissioned, assignment-aware, audit-emitting, and reviewable before clinically relevant actions land. The substrate enforces four-ledger separation by default.

Operations Inbox

Triage queues for field visits, smart visits, provider reviews, referral closures, consent gaps, compliance reviews, audit exceptions, and communication follow-ups.

  • Assignment-aware
  • Ledger-tagged rows
  • Default-deny actions

Smart Visit

Structured CHW visit workflow: consent, readiness, barrier capture, evidence anchors, hybrid note staging for provider review.

  • Voice-friendly capture
  • Audit-emitting evidence
  • Plan-driven prompts

Telehealth Broadcast

Provider-led broadcast to assigned care teams plus on-demand provider loop-in during a CHW field visit. PHI custody stays inside the substrate.

  • Permissioned delivery
  • Audit-emitting joins
  • No third-party widget

Provider Command Center

Single workspace for primary care providers: client header, plan workspace, review queue, telehealth today, audit history, outcomes trends.

  • Real-time CHW visibility
  • Sign-off with audit
  • Care-gap closure

Plan Workspace

Provider-authored plans with versioned goals, care-team tasks, health and social concerns, screening progression. Assignment-aware permissions.

  • Plan versioning
  • Care navigation
  • Compliance readiness

Evidence Ledger

Visit-level evidence records, review packets, referral evidence. PHI-minimized metadata downstream; raw transcripts & audio stay under custody.

  • Synthetic by default
  • Ledger-tagged refs
  • Closed-loop closure

Audit History

Every controlled-state change emits an audit entry, ledger-tagged, scoped to actor and assignment. Always-on, no opt-out.

  • Always-emit
  • Actor + assignment scope
  • Closed by default

PromptOps & AgentOps

Documentation-first governance protocol sequences every non-trivial change. AI agents act inside the workflow graph, never on top of it.

  • Sealed gate trail
  • Bounded authorizations
  • Human review at every gate

Governance

Four ledgers. One audited execution path.

Each ledger lives in its own scope with its own permissions and audit lineage. Clinical routes do not create commercial or workforce records. Cross-ledger references are controlled IDs.

Clinical / CPT

Clinical workflow state · CPT candidates · audit packets. Provider-reviewed.

Commercial / Provider Invoice

Revenue ledger & provider invoice surface. Separate scope. Not touched by clinical routes.

Workforce / Payroll

CHW workforce signals · supervision · time logs. Separate from clinical/CPT.

Platform / Auth / Audit

Identity · permission · consent state · audit emission. The envelope underneath the rest.

Compliance-safe disclaimer

Platform envelope and intent only. No HIPAA, FDA, SOC2, HITRUST, or reimbursement certification claim. No autonomous clinical, billing, payroll, or legal decisioning. Synthetic identifiers only.