The handoff loop your program was built around.
Keep a named owner, recorded status, and next follow-up together. Your team sends referrals through its existing channels and records updates in Teryli. Sending and receiving through Teryli is not live yet. The clinical record stays in the EHR.
The problem
Leaders find out too late.
Referrals scatter
Referrals live in inboxes, spreadsheets, texts, voicemails, and people’s heads.
Teams chase status
Case managers chase programs while admissions and clinical teams do not always see the same status.
Step-downs slip
Step-down work is easier to miss when ownership, readiness, and follow-up are unclear.
Eight steps, one visible loop.
01–02 · Logged & owned
Referral logged, owner assigned — nothing exists until someone owns it.
03–05 · Readiness to next step
Readiness tracked, relevant program facts reviewed, next appointment or operational step confirmed.
- 1Documents receivedA.O.Done 10:15 AM
- 2Program facts reviewedA.O.Done 11:05 AM
- 3Next step confirmedA.O.Confirm bed date · 12:40 PM
- 4TransportUnassignednot confirmed
06–08 · Surfaced & reviewed
Follow-up is surfaced, the team sees recorded status, and activity history supports operational review.
Everything the transition needs, without becoming the clinical record.
Trust boundary & roles
Built beside the EHR, not on top of it.
Teryli is for operational coordination: ownership, readiness, referrals, follow-ups, program-research context, and status visibility. The formal clinical record stays in the EHR.
Each role sees the same transition from their side
The referral that keeps slipping — bring it to the table.
Bring a de-identified example. We will map where it gets stuck and show how the operational loop may fit; do not send PHI or client details.