Referral Source Changes: Preserve Historical Attribution
Preserve referral-source attribution through name changes with a fictional identity crosswalk, historical reporting views, and source-merger test cases.
A referral source name change should preserve the relationship between the source known at the time of referral and the current organization identity, without silently rewriting historical attribution.
A partner can rename, merge, split into separate offices, or change a contact person. Updating a display label may be appropriate while changing the meaning of historical reports is not. Buyers should test which facts are being changed and which reporting view the business actually needs.
Behavioral health referral source name change history
Separate a source identity, its time-specific name, an individual contact, and any later organizational relationship. A name change can describe the same entity; a merger or split can require a different attribution decision. Do not rely on matching text alone to establish continuity. A reviewed crosswalk should explain the actual relationship and its effective context.
Build a fictional source-history crosswalk
Source S-25 is called East Counseling through November 14 and East Community Services from November 15. In this invented example, the reviewed identity remains the same. Requests received before the change retain their original source context. A current-name report can display them under East Community Services if labeled accordingly, while an as-received report uses the earlier name. The two views can reconcile to the same request total.
Distinguish rename from reorganization
Now suppose another office joins the organization on December 1. Historical referrals from that office should not automatically become referrals generated by East before December 1. The business may want a current-group view that includes them, but that view needs an explicit mapping and label. A contact changing jobs is a further separate case: the person's old referrals should not silently move to the new employer merely because a contact record was updated.
Preserve report reproducibility
For a selected receipt cohort, retain the mapping version and the view used. An executive reading a current-group report should know that it answers a different question from an as-received source report. If a prior report is restated, provide a simple bridge showing requests moved between display groups without implying new demand. A changed source label should not change distinct request or person counts unless a separate reviewed identity correction justifies it.
Test search and day-to-day intake
Staff may still receive documents using the earlier name. The process should help them recognize the reviewed source relationship without treating every spelling variant as the same organization. Include similarly named unrelated sources and old contact details in the exercise. The right result is a supported match or a clarification question, not an automatic merge chosen because it produces a tidier source list.
Work through the fictional acceptance exercise
Use a dated source-identity crosswalk with as-received and current-group reporting views, plus rename, merger, and contact-move exceptions. All examples below are fictional.
| Exercise | Starting evidence | Required action | Failure to expose |
|---|---|---|---|
| Pure rename | S-25 changes its reviewed display name on November 15 | Preserve earlier context and label the current-name view | A rename creates new historical demand |
| Office acquisition | Another office joins a group on December 1 | Define any current-group mapping explicitly | All earlier referrals are attributed to the new group as received |
| Contact moves | A partner contact takes a job elsewhere | Preserve the source of earlier referrals | The contact's new employer inherits old attribution |
| Similar names | Two unrelated organizations use similar wording | Clarify the reviewed source identity | Text similarity causes an unsupported merge |
Boundary 1: Pure rename
The relationship can remain stable while the presentation changes; the report should explain which name convention it uses.
Boundary 2: Office acquisition
A present organizational view does not establish the historical source relationship at an earlier date.
Boundary 3: Contact moves
Contact identity and source-organization identity answer different questions.
Boundary 4: Similar names
The matching evidence should establish the relationship rather than rely on cosmetic cleanup.
Two reporting views stay additive after a source joins a group
The selected synthetic cohort contains ten requests: six received from East Counseling and four from Harbor Office. East is renamed East Community Services on November 15 with reviewed identity continuity. Harbor joins the same group December 1; that is a separate organizational event, not another East rename.
Before the group mapping changes, the as-received report shows six East Counseling requests and four Harbor requests. After December 1, a current-group report can show all ten under the present group if it uses the approved mapping and labels that view. The as-received report still shows the original six-and-four split. Neither report contains new requests because of the corporate change.
A prior group report that showed only East's six can be restated as ten under the new current-group definition, with a four-request mapping bridge. That increase is not evidence the renamed East source generated four additional referrals. A contact from Harbor later moving to another employer also does not move those four historical requests to that employer.
Keeping only the latest source text would make the current grouping convenient but destroy the original attribution. Creating new request rows under the group would double-count demand. The dated crosswalk supports both legitimate business views while retaining a ten-request control total and a defensible explanation of the changed grouping.
Observe the work before setting a target
AHRQ’s flowchart tool examines process handoffs.
AHRQ describes observation in simulated settings.
Create ten synthetic referrals spanning the rename date and two later organizational events. Produce both reporting views and reconcile their totals. Then search for the old name and introduce an unrelated similarly named source. Have admissions explain the match while the reporting owner explains the attribution. Any difference in totals should be traced to an explicit population or identity decision rather than concealed in a display-label change.
Questions to settle with the buying committee
Should renaming a source create a new source identity? Establish the actual relationship first. A reviewed pure rename may retain identity, while a merger, split, or unrelated organization requires separate consideration.
Can historical reports use the current source name? They can use a clearly labeled current-name view. Preserve the as-received context and explain the mapping so readers understand the question answered.
Do a contact's old referrals move with a new employer? Do not infer that. Preserve the source relationship at the time of the referral independently of the contact's later employment.
What should reconcile across source-name reporting views? The same selected request population should retain the same control total unless a separate reviewed correction changes the underlying population.
Bring the specimen to a full-platform review
Use the crosswalk to test source maintenance and reporting together. The buyer should be able to explain a current organizational view without losing the source facts attached to earlier referral events.
Ease offers a unified CRM, EHR, and RCM platform for behavioral health. For the source crosswalk, can CRM, EHR, and RCM reviewers reconstruct both as-received and current-group totals without manufacturing new requests at the rename boundary?
Related reading
- Patient Preferences Across Sites: Keep the Offer History
- Rescheduled Consults: Keep the Original Access Clock
Frequently Asked Questions
Should renaming a source create a new source identity?
Establish the actual relationship first. A reviewed pure rename may retain identity, while a merger, split, or unrelated organization requires separate consideration.
Can historical reports use the current source name?
They can use a clearly labeled current-name view. Preserve the as-received context and explain the mapping so readers understand the question answered.
Do a contact's old referrals move with a new employer?
Do not infer that. Preserve the source relationship at the time of the referral independently of the contact's later employment.
What should reconcile across source-name reporting views?
The same selected request population should retain the same control total unless a separate reviewed correction changes the underlying population.
