By SchoolSpan editorial · Reviewed

SchoolSpan / Evaluation guide

EHR or coordination software?
Start with the job to be done.

A practical comparison for providers that want better school coordination without replacing their clinical system.

ONE CONNECTED JOURNEY
School referralA clear starting point
01
Parent consentKnow what is still needed
02
AssignmentCoordinate the next handoff
03
Program visibilityAcross every school
04
Alongside your existing EHR
Explore this page
At a glance

An EHR supports clinical documentation and billing. A school-based coordination layer supports the operational work between providers, schools and families. Whether you need both depends on the gaps in your current workflow, not simply the number of systems you use.

01

Compare responsibilities before comparing tools

QuestionClinical system responsibilityCoordination responsibility
How is care documented?Clinical records and documentationA clear handoff into clinical work
What does the family still need to complete?Clinical intake needs as defined by the providerPaperwork progress and follow-up visibility
What does the school need to know?Keep clinical records appropriately managedProvide authorized operational status
How is capacity coordinated across schools?Clinical and staffing context within the existing systemAssignments, waitlists and school coverage context
What goes into a district program review?Relevant clinical or billing information in its proper scopeService delivery, delays and operational capacity

Individual EHR products differ. This is a responsibility comparison, not a claim that every EHR lacks school-facing capabilities.

02

Audit your current workflow first

Ask the people handling referrals to show how they answer a school’s status question today. Then follow the process for identifying incomplete consent, assigning a referral and preparing a school report.

  • Which steps are handled well by the current EHR?
  • Which steps require a separate spreadsheet or repeated email?
  • Who needs operational visibility outside the clinical team?
  • Where are definitions or records being reconciled by hand?

A coordination tool should address identified gaps. Avoid adding a duplicate process where the existing workflow already works well.

03

Define the handoff between coordination and care

Agree on the event that moves a referral into the clinical workflow, the information needed and who is responsible for the transition. Distinguish operational status from the clinical record.

If integration is needed, confirm the EHR, data fields, direction of transfer and implementation scope. A statement that software works “alongside an EHR” does not automatically mean every system has a ready-made connector.

04

Where SchoolSpan fits

SchoolSpan focuses on school referrals, digital parent consent and intake, assignments, waitlists, authorized school status visibility and reporting across schools or districts. The provider keeps its clinicians and EHR.

It is designed for regional U.S. behavioral health providers serving roughly 10–75 schools. EHR connectivity or a clean handoff should be scoped to the program.

Review SchoolSpan’s coordination capabilities →
Questions, answered

Frequently asked questions

Is SchoolSpan an EHR?

No. SchoolSpan is a school-based behavioral health coordination layer. The provider retains its EHR for clinical documentation and billing.

Should every school-based provider add a second system?

No. Assess the current workflow first. A coordination layer is useful when it addresses a clear operational gap rather than duplicating a process that already works.

Does alongside-EHR positioning imply automatic synchronization?

No. A clean handoff or light integration must be defined. Specific EHR connectivity and automatic synchronization should not be assumed.

Let’s map your program’s next step.

Start with your schools, your current workflow and the coordination gaps you want to close.

Plan a conversation ↗

SchoolSpan works alongside your existing EHR.