Case Study
Health OS — Home-Care Company Suite
A home-care agency's referral-to-discharge operations packaged as twenty PHI-safe workflow automations in one Claude plugin. Client codes in chat, clinical documents assembled for clinician sign-off, and nothing sent externally without human approval.
System Summary
Packaged home-care agency operations as Health OS: twenty workflow automations covering referral intake through discharge, built on the same kit structure as Agency OS and installable as a single Claude plugin.
Business Problem
Home-care coordination is compliance-heavy. Referrals, eligibility checks, assessments, signed care plans, caregiver matching, daily visit documentation, credential expiries, authorizations, billing, and discharge all carry deadlines and privacy rules, and automation that ignores PHI discipline creates risk instead of removing work.
What Czar Studios Built
Twenty workflow kits across six pillars (referrals and admissions, care planning, care delivery, quality and compliance, revenue, people), each a full kit with playbook, handoff contract, templates, and config; seven scheduled n8n companion specs; setup and board utilities; the shared control board; and the same zero-dependency verifier.
Architecture and Data Flow
A PHI layer applies to every kit: chat carries client codes with minimum-necessary detail, records stay in the roster and file systems of record, and clinical documents are assembled from licensed-professional input for signature rather than generated. Cross-workflow contracts are explicit: the documentation audit gates billing prep, a single workflow owns credential expiry, and real-time visit monitoring is separate from after-visit documentation.
Integrations
Claude Cowork and Claude Code skills, n8n companions, and capability-bound roster/CRM, chat, email, file storage, and meeting connectors, with optional scheduling and EVV bindings.
Permissions, Guardrails, and Human Review
Administrative automation only, with no clinical judgments and no medical advice. Family- and payer-facing documents stay drafts until a human approves, incident severity resolves from the agency's own policy matrix, headless runs post codes and counts only, and filled configs are gitignored so real payer and policy data never enters the repository.
Testing and Verification
The cross-suite verifier passes with zero failures: twenty kits, globally unique trigger phrases, seven companion specs syntax-checked, and board data matched to the kits. The board is render-verified in both themes.
Practical Outcome
The same kit structure now covers a second industry. A care business can fork the package, fill the config including its own policy matrices, and run PHI-disciplined workflows against its own connectors.
Privacy-Safe Proof Notes
Public repository with all twenty kits, the verifier, and the control board; screenshots show the board and the handoff map. The project contains workflow definitions only, with no client, caregiver, or payer data. Claude assisted the implementation; Czar Studios owned the design, the PHI rules, verification, and release.
Project Gallery
