Define behavioral health referral-source reporting across requests, people, appointment events, and admissions with clear attribution and privacy review.
Referral-source reporting should define the request, person, attribution rule, conversion event, and privacy boundary before a source is credited with an admission. Otherwise a polished funnel can blend several different events into an apparently precise conversion rate.
This guide describes operational reporting for behavioral health organizations. It does not authorize marketing disclosures, determine patient eligibility, or prescribe a universal attribution model. Use the organization's approved privacy, clinical, and reporting processes for the actual information and tools involved.
Behavioral health referral source reporting starts with units
Define whether the report counts messages, requests, unique people, appointments, attended visits, admissions, or another event. One person can have several requests over time, while a repeated transmission can concern one request.
The ASTP/ONC SAFER patient identification guide provides a safety reference for person identification. Follow the organization's approved process rather than using a similar name or contact detail as the sole basis for combining records.
Keep request identity separate from person identity. A later request for another program can be legitimate without creating a second patient identity. A repeated message can be associated with an existing request without erasing its source and receipt history.
Define what source means
Source can mean a referring organization, a person who suggested care, the channel through which a request arrived, or a marketing attribution category. Those fields answer different questions and should not be silently substituted.
Create a source dictionary with the field purpose, allowed values, evidence, entering role, correction owner, and reporting use. A web inquiry and a hospital referral can both arrive through a form while representing different source relationships.
Use a fictional example in which a person hears about the clinic from one source and later submits a request through another channel. The organization can retain both facts while applying a defined reporting rule. It should not overwrite one to make the pipeline simpler.
Preserve the attribution rule and uncertainty
Choose an attribution approach appropriate to the report's purpose and document it. First known source, latest request source, self-reported source, and another reviewed rule can produce different results. The report should state which one it uses.
Keep unknown or conflicting information visible. An unknown category is more honest than assigning a source without evidence. Give staff a route to correct a mistaken entry while preserving relevant history.
The Health IT Playbook provides workflow and implementation resources. Treat source reporting as a process involving definitions, staff actions, and data ownership rather than only a dashboard configuration.
Name the conversion event precisely
An appointment offer, booking, attended visit, admission, and completed intake are different events. The organization may want several measures, but each needs its own definition and dates.
For a fictional cohort, some requests receive an offer, some book, and some attend. A report based on bookings should not be labeled attended-care conversion. If the organization reports admissions, define the actual admission event under its approved process.
Keep clinical decisions separate from marketing reporting. A source category should not determine clinical eligibility or urgency. Authorized clinical professionals make care decisions using the actual circumstances and policies.
Review privacy boundaries before sharing data
Referral and intake information can be sensitive. Have authorized privacy, legal, and security staff review the data, purpose, recipients, access, agreements, and tools involved in any reporting flow.
The HHS business associate guidance is a relevant reference when evaluating outside services handling protected information. It does not establish that a particular marketing platform or disclosure is appropriate; the actual arrangement needs review.
Use aggregate or otherwise approved information for broader reporting where appropriate under that review. Avoid copying detailed intake or clinical narrative into general marketing workspaces merely because it helps explain a conversion.
Reconcile source reports to known events
| Reporting element | Definition to retain |
|---|---|
| Unit | Request, person, message, appointment, or admission |
| Source | Referral relationship, arrival channel, or attribution category |
| Rule | How credit is assigned when several facts exist |
| Event | The actual conversion being counted |
| Period | Which date determines inclusion |
| Duplicate treatment | How repeated messages and new requests differ |
| Privacy scope | Who can see the result and supporting detail |
Create a fictional dataset with repeated messages, a new request from an existing patient, conflicting sources, a booked appointment, and an attended visit. Write expected results under the approved rules before running the report.
Reconcile individual cases as well as totals. One duplicate and one missing request can offset each other. A matching total is not enough if the wrong source received credit or the conversion event is misidentified.
Test historical changes and staff handoffs
Correct a fictional source after an appointment occurs. Determine whether historical reports update, retain the earlier classification, or need a documented revision. The organization should know how source corrections affect comparisons.
Have another intake staff member take over the request using only the recorded history. They should understand the source information, current status, prior contact, and next action. A reporting field should not replace operational ownership.
If the proposed system imports source information, identify mappings, defaults, and failure states. A missing value should not silently become a preferred channel or a generic category whose meaning changes over time.
Use results to improve the actual intake process
Compare sources only with compatible definitions and appropriate context. Different request types can involve different services, timing, and operational work. Avoid treating one aggregate conversion rate as a complete measure of source quality.
Inspect unresolved requests and barriers alongside completed events. A source can appear less productive because work waits at a handoff rather than because the requests are inappropriate. Use the findings to clarify process ownership.
Ease Health publishes this guide and offers a unified CRM, EHR, and RCM platform for behavioral health. Ask vendors to demonstrate the proposed source model, privacy boundaries, and reporting definitions. Related material includes the CRM overview, intake status guide, and duplicate-referral review guide.
The useful result is a source report that explains what it counts and what it knows. That supports better decisions without confusing a marketing category with a patient's clinical journey.
Related reading
Frequently Asked Questions
Is a referral count the same as a unique-person count?
No. One person can generate several legitimate requests, and one request can arrive more than once. Define the counting unit and duplicate treatment before comparing sources.
Does an appointment booked equal an admission or attended visit?
No. Booking, attendance, admission, and other conversion events are distinct. Name the event used by each report and preserve the underlying history.
How should conflicting source information be handled?
Preserve the reported source, evidence, date, and the organization's approved attribution rule. Record uncertainty rather than silently overwriting the history to fit a preferred channel.
Can intake details be sent to marketing tools without review?
Do not assume that. Authorized privacy, legal, and security staff should review the actual information, purpose, recipients, agreements, and tools. Operational reporting does not itself establish an appropriate disclosure.
