CareHub - Next.js + Azure Backup Plan
Last updated: 10/20/2018
CareHub - Next.js + Azure Backup Plan
Executive Summary
CareHub is a California Workers' Compensation mental health platform that connects injured workers with psychological evaluation and therapy services. The system manages the full lifecycle from intake through treatment completion, with specific compliance requirements for CA Labor Code 3208.3.
Why This Backup Plan
The original implementation on Blaze.tech proved challenging due to:
- Tedious UI configuration for complex forms
- Limited automation capabilities
- Difficulty implementing custom workflows
- Slow iteration cycles
This backup plan outlines a complete rebuild using Next.js deployed on Azure services, giving full control over the implementation.
Quick Links
| Document | Description |
|---|---|
| 01-PROJECT-OVERVIEW.md | Business context, objectives, stakeholders |
| 02-USER-STORIES-JTBD.md | Jobs To Be Done organized by role |
| 03-DATABASE-SCHEMA.md | Complete database schema |
| 04-PORTALS-AND-FEATURES.md | Portal-by-portal breakdown |
| 05-WORKFLOWS-AND-AUTOMATION.md | Automated workflows |
| 06-AI-INTEGRATION.md | AI features and prompts |
| 07-COMPLIANCE-REQUIREMENTS.md | CA WC specific requirements |
| 08-AZURE-ARCHITECTURE.md | Recommended Azure architecture |
| 09-TECH-STACK.md | Technology recommendations |
System Overview
User Roles
| Role | Portal | Description |
|---|---|---|
| Care Coordinator | Admin Portal | Manages cases, assigns staff, coordinates care |
| Member | Member Portal | Injured worker receiving treatment |
| Psychologist | Psych Portal | Conducts evaluations, creates care plans |
| LPCC | LPCC Portal | Provides ongoing therapy sessions |
| System Admin | Admin Portal | User management, system configuration |
Core Workflows
1. INTAKE FLOW
Claim Referral → Create Case → Send Intake Form → Member Completes → AI Analysis
2. EVALUATION FLOW
Psychologist Assigned → Review Intake → Conduct Evaluation → Create Care Plan →
Determine Causation → Transfer to LPCC (or Keep)
3. TREATMENT FLOW
LPCC Assigned → Schedule Sessions → Document Sessions → Track Progress →
Request Extensions → Discharge at MMI
4. COMPLIANCE FLOW
Causation Analysis → GAF Scoring → MMI Determination → Generate Reports
Key Differentiators
AI-Powered Clinical Support
- Intake analysis with risk assessment
- Session transcript summarization
- Care plan suggestions
- Progress assessment
California WC Compliance
- Causation analysis (Industrial vs Non-Industrial)
- MMI tracking
- GAF scoring
- PR-2/PR-4/RFA document generation
Member Engagement
- Daily/weekly check-ins
- Progress visualization
- Mobile-optimized interface
Implementation Status (from Blaze)
| Phase | Description | Status |
|---|---|---|
| Phase 0 | Project Setup | Completed |
| Phase 1 | Foundation Tables | Completed |
| Phase 2 | Admin Portal | Completed |
| Phase 3 | Intake Form | Completed |
| Phase 4 | Psychologist Portal | Not Started |
| Phase 5 | LPCC Portal | Not Started |
| Phase 6 | Member Portal | Not Started |
| Phase 7 | Workflows | Not Started |
| Phase 8 | AI Integration | Not Started |
| Phase 9 | Testing | Not Started |
| Phase 10 | Causation/Compliance | Not Started |
Reference Implementation
A reference Next.js implementation exists at:
/Users/briancline/Documents/DEV/carehub-demo
Use this to compare features, field names, and implementation patterns.
Getting Started with Next.js Build
- Review 08-AZURE-ARCHITECTURE.md for infrastructure setup
- Review 03-DATABASE-SCHEMA.md for data model
- Start with Admin Portal (Phase 2 equivalent)
- Implement Intake Form (Phase 3 equivalent)
- Continue through portals in order
Key Decisions Made
- Session Authorization: Default 7 sessions per case
- Session Duration: 50 minutes standard
- Check-In Frequency: Weekly recommended, daily supported
- Causation Timing: Typically determined around 3rd session
- Document Types: PR-2 (per session), DFR, RFA (extension), PR-3, PR-4, Care Plan
- Claim Types: Physical-Mental, Mental-Mental, Mental-Physical