Plan MHOTRS Social Care Network handoffs with distinct screening, referral, eligibility, service, and billing responsibilities in New York.
A social care handoff should distinguish a screening finding from a referral, eligibility decision, delivered service, and billing event. Combining those events into one complete status can hide the exact point at which a person is waiting for help.
This guide addresses operational planning for New York MHOTRS programs considering Social Care Network workflows. It does not establish network participation, eligibility for a service, or a payment entitlement. Those questions depend on current program guidance, agreements, and the actual circumstances.
MHOTRS Social Care Network handoff: start with program evidence
The OMH MHOTRS and Social Care Networks guidance provides a program-specific starting point. Review it with the organization's responsible program and billing leads before translating a proposed relationship into software requirements.
List the organizations involved, proposed services, responsible contacts, agreements, and unresolved questions. Separate what the clinic currently does from what it hopes to add. A system configuration should reflect an approved operating arrangement rather than create the appearance that one already exists.
Use current source documents and record the review date. Program arrangements can change, and an old implementation worksheet can become misleading if staff assume it remains authoritative indefinitely. Assign an owner to check for relevant updates.
Map events without assuming they are equivalent
A screening finding records information. A referral communicates a request or handoff through an approved process. A receiving organization's acknowledgment establishes receipt. An eligibility decision and a delivered service are further events with their own evidence.
Write the event sequence in plain language and identify which organization can observe each step. The clinic may know that a referral was sent without knowing whether a service occurred. Reporting the latter based on the former would overstate what the record supports.
For a fictional example, a person reports a transportation barrier. Staff review the finding, initiate an authorized handoff, receive acknowledgment, and later seek an update. Each event should remain identifiable. The original screening result should not automatically become a completed service record.
Assign ownership across organizational boundaries
Identify the sending contact, receiving contact, acknowledgment method, follow-up owner, and backup route. An external handoff can stall when each organization assumes the other is responsible for the next action.
Define what the clinic does when information is incomplete, the receiving organization does not acknowledge receipt, or the proposed pathway is unavailable. Keep those actions within the organization's approved program and clinical processes. A generic pending status is not enough if nobody has authority to move it forward.
Separate coordination from eligibility and service decisions. A clinic staff member may help collect information or communicate a question without being the person authorized to determine program eligibility. The worksheet should identify the actual decision owner.
Review information sharing before building integrations
Have authorized privacy and legal staff review the information, purpose, parties, and communication route. The operational value of coordination does not remove the need to evaluate appropriate sharing for the actual circumstances.
The OMH guidance index lists related resources on information sharing and treatment collaboration. Use those as starting references for specialist review, alongside the Social Care Network guidance and relevant agreements.
During software discovery, identify every place information will appear: chart, referral message, external portal, worklist, export, and support ticket. Keep broad operational displays limited to information appropriate for their users. A linked clinical record may be safer and clearer than copied narrative in several tools.
Distinguish software functions from external arrangements
A screening form does not prove that the system creates a referral, sends it to a network partner, tracks acknowledgment, or confirms a delivered service. Ask the vendor to demonstrate each proposed step separately.
Record whether the step is available functionality, customer configuration, an external service, manual coordination, or future development. Identify any agreement, account, enrollment, or technical dependency involved. A demonstration in a prepared environment can conceal work the clinic will need to own.
| Proposed step | Evidence to request |
|---|---|
| Record a finding | Structured result and its source |
| Initiate a handoff | Actual sending workflow and responsible user |
| Confirm receipt | Receiving acknowledgment or documented manual process |
| Track next action | Named owner, status meaning, and follow-up history |
| Confirm service outcome | Evidence from the organization that can establish it |
Avoid describing a workflow as fully automated when staff still reconcile statuses manually. Manual work can be a legitimate design choice, but the organization should know its scope and staffing needs.
Keep financial review separate from coordination
Have the billing and program leads identify the actual payment pathway and responsibilities, if any, for each proposed service. Do not infer a billable event from a screening finding or a referral status.
Record which organization delivers the service, which evidence supports the event, and who reviews the financial treatment. If a network partner makes an eligibility decision or maintains the service record, document how the clinic receives appropriate confirmation without overstating its own information.
Use fictional cases to test the distinction between a request, a declined or unavailable pathway, an accepted handoff, and a confirmed service. The report should make those outcomes distinguishable rather than counting all referrals as delivered help.
Pilot one pathway with an explicit exception list
Choose a narrow, approved workflow and run a small fictional test pack before expanding. Include incomplete information, duplicate contact, no acknowledgment, an unavailable pathway, and a later status update.
Ask staff from each participating organization to explain their next action. If the answers conflict, resolve the agreement or workflow issue before adding more software. Measure unresolved handoffs and the intervals between named events rather than relying on a single completion percentage.
Ease Health publishes this guide and offers a unified CRM, EHR, and RCM platform for behavioral health. Ask vendors to prove the proposed workflow step by step and identify what remains external or manual. Related material includes the EHR overview, hospital referral handoff guide, and intake access dashboard.
The useful output is an agreed pathway with evidence-backed statuses and accountable exceptions. That makes coordination more transparent without confusing a recorded need with a completed service.
Related reading
Frequently Asked Questions
Does a social-needs screening result mean a referral was completed?
No. Screening identifies information for review. Referral, receipt, eligibility, service delivery, and follow-up are separate events with their own responsible organizations and evidence.
Can an EHR screening form establish Social Care Network participation?
No. Review the applicable New York program guidance, network arrangements, and organizational responsibilities separately. A software form does not establish an agreement, eligibility, or payment pathway.
What should a MHOTRS handoff worksheet include?
Identify the clinic and receiving contacts, the authorized information route, the event being handed off, outstanding questions, expected acknowledgment, and follow-up owner. Keep clinical and program eligibility decisions distinct.
What should a vendor prove about a social care workflow?
Ask the vendor to demonstrate each proposed step and identify external services, agreements, configuration, and manual work. Do not infer referral tracking or service confirmation from the presence of a screening tool.
