In late 2023, California's $4B Children and Youth Behavioral Health Initiative needed something the state had never built before: a way for school districts to deliver — and bill for — school-based behavioral health services at scale. This is what it took to build the infrastructure underneath that ambition.
The context.
California's Children and Youth Behavioral Health Initiative is one of the largest public investments in youth mental health in US history. The program's premise is simple in language and unprecedented in operations: meet kids where they are — at school — and pay providers to serve them through the CYBHI plumbing that funds hospitals and clinics.
The core challenge lies in a fundamental structural mismatch: educational institutions are not healthcare enterprises. Local Education Agencies — including county offices, school districts, and charter networks — traditionally operate entirely outside the clinical ecosystem, lacking the foundational infrastructure required for medical revenue cycles: enterprise EHRs, Charge Description Masters, payer enrollment networks, automated claim-scrubbing logic, and dedicated denial-management workflows. They have student information systems and instructional staff. The gap between those two worlds is the problem this engagement existed to close.
What had to be built.
The county office mandate covered native Local Education Agencies serving roughly 120,000 students, with the obligation to bill cleanly against the CYBHI fee schedule, and the Medi-Cal Billing Option Payment program for participating LEAs.
The work fell into four layers, designed and stood up in parallel:
Engineered from a comprehensive blueprint spanning system architecture, granular user roles, and complex business logic, the platform supports a diverse ecosystem of stakeholders — including providers, clinical supervisors, billing coordinators, administrators, and LEA business officials. Each user interacts with role-based dashboards tailored precisely to their operational metrics. The suite features seven distinct dashboards, derived from extensive stakeholder discovery to mirror true day-to-day workflows, natively supporting individualized Care Plans, Coordination of Services Team (COST) frameworks, and end-to-end referral pipelines.
Seamlessly integrating with Student Information Systems (SIS) to drive advanced analytics and granular whole-child tracking. By designing and orchestrating scheduled ETL pipelines, the system automatically ingests, normalizes, and routes critical clinical datasets directly into ESHR — providing the foundational, high-integrity data required to power compliance-driven billing and revenue cycle operations.
Established a Charge Description Master, claims-scrubbing logic, reimbursement-rate tables, and full 837P billing workflows for three different programs simultaneously: the CYBHI multi-payer fee schedule, Medi-Cal BOP, and Managed Care Plan billing. Each program has its own rules, its own forms, its own gotchas — and providers do not have the luxury of caring which is which. The system has to.
No ESHR survives contact with its users unless someone is on the other end of the help line. Set up the helpdesk function, the support forums and technical assistance framework — and instituted a standing enhancement-and-bug-fix governance process so the system keeps getting better instead of slowly worse.
The system, in brief.
- ESHR Platform Salesforce (customized over a Salesforce-based EHR system)
- Data Warehouse Azure SQL with custom ETL pipelines
- Claims Submission 837P via Availity clearinghouse and 837I to Medi-Cal
- Payment Reconciliation Carelon TPA / Payspan and Medi-Cal
- Programs Covered CYBHI fee schedule · Medi-Cal BOP · MCP Billing
- Compliance HIPAA · Medi-Cal · FERPA
- Coverage Local Education Agencies · Community-Based Organizations · 120,000+ students
What the numbers say.
The numbers above are presented for what they are: directional indicators of a system that works, not the final measure of it. A 90% clean-claim rate is a meaningful threshold for a Medi-Cal billing operation — particularly one running against three programs simultaneously, on a platform that did not exist two years ago.
The other measure — harder to quantify but more important — is that ten LEAs now have a way to fund the people doing the work. A district that hires a counselor knows the claim will go through. A county business official can answer the question "did we get paid for that?" without a forensic exercise. That is what the system is for.
What it taught me.
The work continues. The system gets better. The next chapters — adding LEAs, expanding programs, integrating more deeply with the state's data infrastructure — are still being written.