Design school satellite intake handoffs for an Article 31 clinic, with clear referral ownership, family contact, scheduling, and record boundaries.
A school satellite intake workflow should make referral receipt, authorized contact, clinical review, and appointment responsibility explicit across the school and clinic. A referral can be important without being an admission, and a shared interest in a student does not make every participant responsible for the same next step.
This guide addresses operational handoffs for New York Article 31 programs working in school settings. It does not decide an individual student's consent, privacy, clinical, or educational rights. Those decisions belong with the clinic's authorized clinical, privacy, and legal leads using the applicable facts and rules.
Article 31 school satellite intake starts with boundaries
The OMH MHOTRS programmatic guidance includes school-based satellite guidance. Use that reference together with the clinic's operating documents and school agreements to define the actual service relationship.
Write down which organization receives a referral, contacts the family or other authorized person, conducts clinical review, schedules care, and communicates an appropriate disposition. The same person may coordinate several steps, but the responsibilities should remain distinguishable.
Map the information boundary as carefully as the task boundary. A referral form, a school record, and a clinic chart can serve different purposes. Ask the privacy lead to approve the proposed flow and access before software staff create a shared mailbox, portal role, or export.
Give every referral a stable identity
Use a stable referral identifier and record the date received. Match the referral to an existing patient through the clinic's identity process rather than creating a new chart whenever a name arrives with a different spelling or contact detail.
Record the source and authorized contact route without copying unnecessary narrative into an operational tracker. A referral log can often coordinate work with status, owner, dates, and an appropriate link to the underlying record. Sensitive details should remain in the authorized location.
For a fictional example, the school sends a referral on Friday and a family member contacts the clinic Monday. Staff should be able to recognize the same request and preserve both events. Otherwise the clinic may report two referrals, contact the family twice, or lose the original handoff history.
Separate contact work from clinical decisions
An intake coordinator can confirm receipt and arrange the next step, but clinical review follows the clinic's own process. Do not ask administrative staff to infer urgency from a free-text referral or use a queue's age as a substitute for assessment.
Define the route for concerns that need clinical attention. Staff should know who is available, how to document the handoff, and what to do when the usual contact is absent. Keep that route aligned with established clinic and school procedures rather than inventing an escalation channel inside a spreadsheet.
Also distinguish unsuccessful contact from a decision that the person does not need care. A lack of response may call for another action under clinic policy; it is not a clinical conclusion. Use statuses that describe what staff know and what happens next.
Design communication around authorization
Before sending updates, determine who is authorized to receive which information and through what channel. The OMH guidance index includes resources on minors' treatment rights and information sharing. Those are reference points for the clinic's specialist review, not shortcuts to a universal rule.
Keep operational confirmations carefully scoped. Even a seemingly simple status message can reveal that someone is seeking or receiving services. The approved communication plan should cover acknowledgment, scheduling outreach, referral disposition, and requests for additional information.
When evaluating software, ask what a school-facing user can see, what a family-facing user can see, and what clinic staff can see. Test separate accounts. A screenshot of a filtered list is not evidence that the underlying chart has an appropriate access boundary.
Plan for school calendars and clinic coverage
School breaks, closures, testing days, and space changes can interrupt a workflow that works during an ordinary week. Record who owns unresolved referrals during a closure and how patients receive accurate contact and appointment instructions.
Use a fictional referral received just before a holiday break. Walk through receipt, authorized outreach, clinical review, and scheduling. If the school-based room is unavailable, determine who explains the available alternatives under the clinic's approved operating arrangements.
Keep primary-clinic and satellite responsibilities explicit. A school closure does not automatically answer where or how a clinic service can occur. Operations should confirm the appropriate arrangement, and the software configuration should reflect that decision rather than make it implicitly.
Build a handoff worksheet staff can use
| Handoff | Evidence to retain |
|---|---|
| School to clinic | Referral identifier, receipt date, and clinic owner |
| Intake to clinical review | Question needing review and responsible clinician |
| Clinic to authorized contact | Approved channel, date, and outcome of contact |
| Review to scheduling | Disposition, next action, and scheduling owner |
| Unresolved referral to coverage staff | Current status, outstanding action, and backup owner |
Treat the worksheet as an operational design. The exact fields and access depend on the clinic's approved process. Avoid building a parallel clinical record in a broadly shared tool simply because it is convenient.
Review the worksheet with school and clinic counterparts using fictional cases. Ask each person to explain what they would do next. Conflicting answers reveal an agreement or training issue that software alone will not resolve.
Evaluate the workflow before expanding it
Pilot a small set of referral patterns: a new patient, an existing patient, incomplete contact information, a duplicate referral, a family-requested delay, and a referral arriving during a closure. Confirm that each has an owner and a documented next step.
Measure unresolved handoffs and time between clearly defined events. Keep referral receipt, first outreach, appointment offer, scheduled date, and attended care separate. An apparent improvement can result from changing a timestamp definition rather than making access easier.
Ease Health is the publisher of this guide and sells behavioral health software. Ask any vendor to demonstrate the proposed school satellite workflow, including access boundaries and exception handling. Related material includes the CRM overview, satellite setup checklist, and intake access dashboard.
The work product is a clear handoff agreement backed by a tested workflow. Its value is that a referral remains accountable through ordinary staffing changes and school calendar disruptions.
Related reading
Frequently Asked Questions
Does a school referral mean a student is enrolled in clinic care?
No. Referral receipt is one event. The clinic still follows its applicable intake, clinical, consent, and enrollment processes. Keep the referral status distinct from admission and appointment attendance.
Should school staff receive unrestricted clinic chart access?
Do not infer chart access from the referral relationship. The clinic's privacy and legal leads should define appropriate information sharing and access under applicable law and agreements.
What should a school satellite intake handoff include?
Use the minimum information appropriate to the handoff: a stable referral identifier, date received, responsible contact, current status, next action, and authorized communication route. Keep clinical narrative in the appropriate record.
How should a clinic prepare for school breaks?
Define contact coverage, appointment options, unresolved referral ownership, and patient-facing instructions before the break. Test the workflow using a fictional referral that arrives just before a closure.
