A simpler coordination experience for school staff working with their behavioral health provider.
SchoolSpan gives authorized school staff role-limited operational visibility into referrals to a participating behavioral health provider. It helps schools follow progress while full clinical records remain in the provider’s existing EHR.
Your behavioral health provider uses SchoolSpan to coordinate its school-based program. Authorized school staff can participate in referral and status workflows within the access established for their role and school relationship.
SchoolSpan’s primary customer is the provider organization. School teams should confirm access, referral expectations and the information-sharing process with their provider before rollout.
The portal is designed to answer appropriate operational questions about referral progress. The examples below illustrate possible stages; they are not a promise that every role can see every stage.
| Illustrative status | Operational meaning | Useful coordination question |
|---|---|---|
| Referral received | The referral is in the provider’s workflow. | Is anything else needed to begin coordination? |
| Consent or intake pending | A required family step is not yet complete. | Who is responsible for the next follow-up? |
| Awaiting assignment | The provider is coordinating the next care handoff. | Does the provider need any operational context? |
| First appointment scheduled | A first visit has been scheduled. | Is any appropriate school coordination still needed? |
The visible fields depend on provider configuration, permissions, applicable authorizations and information-sharing agreements. Operational status can be sensitive, even when it does not include clinical notes.
Clinical documentation, treatment records and billing workflows stay in the provider’s EHR. SchoolSpan is designed for coordination around care, rather than a school-facing clinical chart.
Provider and school teams should decide what each role needs for its coordination responsibilities. More information is not automatically more useful; the right scope is the information appropriate to that role and purpose.
Review the information-sharing approach →A referral can generate repeated “any update?” emails when the school cannot tell whether the provider received it or which step is pending. A shared operational status helps focus the conversation on the next action.
Illustrative example: Instead of asking for a general update, an authorized school contact sees that a referral is awaiting a family step and coordinates the next appropriate follow-up with the provider. The school does not need a treatment note to understand that operational stage.
This is the intended coordination benefit, not a measured claim about school staff time or adoption.
Families should follow the provider’s process for care questions. SchoolSpan provides software; the provider remains responsible for clinical care.
SchoolSpan is designed around a provider organization’s multi-school program. School staff participate through the referral and status process established with that provider.
The school portal is intended for role-limited operational updates, not access to the provider’s full clinical chart. Clinical records remain in the provider’s EHR.
Not necessarily. An appointment scheduled status is different from an appointment attended measure. Provider and school teams should agree on the meaning of each visible status.
Access should follow the program’s agreed permissions, applicable authorizations and information-sharing requirements. Confirm specific roles and fields with the provider before rollout.
Start with your schools, your current workflow and the coordination gaps you want to close.
Plan a conversation ↗SchoolSpan works alongside your existing EHR.