BHPM · Public Record

Deliverable 03 · Activity 3.5

Technical Assistance Plan

Training, Technical Assistance, Coaching And Implementation Support For Six LEAs And Eighteen Schools.

The Technical Assistance Plan describes how the Santa Clara County Office of Education and project partners will provide ongoing training, technical assistance, coaching, and implementation support to the six participating local educational agencies (LEAs) and eighteen participating schools across the contract period.

Due
September 30, 2026
Term
July 1, 2026 to June 30, 2028
Elements
9
Lead
SCCOE · Impacter Pathway · DBG
Activity 3.3 · The CurriculumThe Plan As A PDF · 34 pp

Exhibit A Section VI, Deliverable 3 · Nine required elements · Implementation Workplan Activity 3.5

Activity 3.5 · Section 07

Platform Deployment And Operational Implementation

What deployment involves at each site, who does it, and the agreements and disclosures that sit around it.

Activity 3.5 · Due September 30, 2026SCCOE · Impacter Pathway · DBG

Scope This Section Answers

Deploy an operational behavioral health screening and performance management platform across all 18 school sites, including technology configuration, SIS integration, reporting workflows, data privacy agreements, CYBHI fee schedule activation, as well as related implementation supports.

Deployment Across The Eighteen Sites

Impacter Pathway leads deployment of the behavioral health screening and performance management platform at all eighteen participating schools under activity 3.2, running from August through November 2026.

Deployment at a site covers technology configuration, student information system integration, single sign-on provisioning, rostering, account and access setup, role-based permissions, devices and audio, and preparation and testing before the first screening window. The sequence and the specifics differ by district, because the student information systems, identity providers, and device arrangements differ.

Working With LEA And Site Technology Staff

Each LEA identifies a technology specialist or team, and Impacter Pathway's Customer Success and Enablement team works with them directly. Where a school designates a site technology lead or teacher technology lead, that person is included. Districts use different identity providers, so single sign-on is configured through Clever, Google, or whichever provider the district already runs. Rostering method and synchronization schedule are set the same way.

The LEA technology contact is an implementation partner. They know the district's systems, its constraints, and its change windows, and deployment is planned around what they advise.

Data Privacy Agreements

Data privacy agreements are in place before student data moves. The project operates under the California Student Data Privacy Agreement and a master services agreement carrying children's online privacy terms, both executed between Impacter Pathway and SCCOE and published in the project's resource library. Agreements at the district level are confirmed with each LEA as part of deployment.

Stanford University School of Medicine contributes expertise in data governance, regulatory compliance, data security, and privacy through its Data Core. Breaking Barriers California advises on privacy law and scope of practice questions as they arise.

CYBHI Fee Schedule

Participating LEAs come to this work with different positions on the Children and Youth Behavioral Health Initiative fee schedule, and several already bill under it. Milpitas Unified School District, Sunnyvale School District, and San Diego Unified School District have each drawn reimbursement. Mount Pleasant Elementary School District and Lake Tahoe Unified School District are published cohort participants with no reimbursement recorded. Rio School District works under a county capacity grant and carries two CYBHI-funded associates in a licensure pathway.

Fee schedule activation during deployment therefore means different things across the cohort. Where an LEA already bills, activation is a matter of configuring the platform to support the workflow the district runs. Where it does not, activation connects to the billing readiness work already under way there. Deliverable 1 records each district's position, and deployment starts from it.

Capacity building on the fee schedule itself, and the wider financing and sustainability questions around it, is addressed in the system leadership pathway of the Activity 3.3 curriculum. Breaking Barriers California provides the subject matter expertise on fee schedule implementation and Medi-Cal sustainability, and the fee schedule scope, rates, and codes are published in the project's resource library.

Reporting Workflows

Reporting views are configured so that each role sees what is appropriate to it. Authorized practitioners see roster-synced student-level information. School teams see grade, group, and schoolwide aggregates. LEA leadership sees school aggregates and cross-site views. These views are configured during deployment, because the first screening window produces information people need to be able to read immediately.

Technology Disclosure

Activity 3.8 completes the GenAI reporting and factsheet disclosure covering third-party transcription used in the service documentation workflow, as required by Exhibit C sections 20 and 56 for previously unreported technology. Impacter Pathway carries this from September through November 2026.

Activity 3.3 is the training and capacity-building curriculum this plan draws on. It is cited here rather than reproduced. · Exhibit A Section VI, Deliverable 3 · Nine required elements · Implementation Workplan Activity 3.5