# Referral reconciliation: pre-migration inventory | SourceX

Canonical: https://refer.sourcex.si/guides/workflow-appointment-referral-reconciliation
Last updated: 2026-11-04

Before an administrative platform migration, inventory the full life of a referral, not just its open or closed status: the original referral request with its intended service and location, every scheduling event, the work-queue or service desk notes made when a request could not be matched, the location and provider mapping tables, and the closure confirmation. Record which system holds each, how many years exist, who controls the records under the company's contracts and when legacy access ends.

## What should be inventoried before an administrative platform migration affects appointment referral reconciliation history?

Record classes, years, volumes, owners, contract limits and the real access deadline, all as metadata. Work through it with the administration director in one sitting; none of it requires seeing a referral.

1. **Record classes.** Referral requests, scheduling events, unmatched work-queue entries with reason codes, service desk tickets, mapping change requests, closure confirmations.
2. **Coverage.** The year each system went live, how many practices or locations it served, and whether older referrals sit in a previous platform or on a fax server.
3. **Volume, roughly.** Referrals a year and roughly how many needed manual handling before they could be booked; an order of magnitude is enough.
4. **Migration scope.** Which classes move, which stay read-only and which are retired; whether historical mappings and status histories travel with the referrals.
5. **Access deadline.** The date legacy access ends, from the contract.
6. **Contracts.** Whether the company is a covered entity or a business associate for these records, and what its agreements say about secondary use.

Do not recommend keeping data longer than the company's retention schedule and agreements allow, and never collect exports, screenshots, reports or logins. Much of the referral back-and-forth sits in shared mailboxes; the [email platform migration handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-an-email-platform-migration) applies the same discipline there.

## Why does reconciliation history fall out of a platform migration?

Because a migration plan is built around what the new platform needs to schedule tomorrow, and reconciliation evidence lives in the gaps between systems. Open referrals and future appointments move. The work-queue entry made when a request named a retired site, the service desk ticket that remapped a location code and the old mapping table itself are rarely in scope.

The closure step is the one most worth protecting. The CMS50 quality measure treats a referral loop as closed only once the referring clinician gets a report back from the clinician who saw the patient; in its current version, a procedural report counts. The ONC's 360X closed-loop referral guide describes the same chain from the interoperability side: the recipient accepts or declines a referral request, the result of the referral closes the loop, and a unique referral ID lets the returned note be matched across systems. If the referral IDs or the location mappings that tied them together do not travel, a closed loop in the old platform can look like an orphaned request in the new one.

## An illustrative inventory sheet

Illustrative only; the company and figures are fictional. A 300-person management services company runs central scheduling for a group of affiliated practices and is moving to a new administrative platform. Its administration director fills in the sheet in one meeting, from the migration plan and memory, without opening a referral.

| Record class | System | Years held | Owner | Migration scope | Reachable until |
|---|---|---|---|---|---|
| Referral requests | Legacy scheduling platform | 2017 to now | Administration director | Open referrals only | Legacy contract end |
| Scheduling events | Legacy scheduling platform | 2017 to now | Administration director | Future appointments only | Legacy contract end |
| Unmatched work-queue notes | Legacy work queue | 2018 to now | Intake supervisor | Not in scope | Legacy contract end |
| Location and provider mappings | Legacy platform tables | Current version only, history in tickets | IT applications lead | Current mapping only | Legacy contract end |
| Mapping change tickets | Service desk | 2019 to now | IT service desk manager | Stays in service desk | Service desk retention |
| Closure confirmations | Document management | 2016 to now | Health information manager | Read-only archive | Document retention schedule |

Reading the sheet: the work-queue notes and the mapping history are the evidence of how exceptions were resolved, and both end with the legacy contract. Whether the company may keep or reuse them is a separate question, answered by its retention schedule and its agreements with the practices, not by the partner.

## Ask the administration director about coverage and rights

The administration director usually knows coverage. Rights are the harder part in healthcare administration. Under HIPAA, a business associate contract must set out the permitted and required uses and disclosures of protected health information by the business associate, and it cannot authorize a use the covered entity itself could not make. A management services or billing company often holds referral records under such agreements, so the practices or health system may hold the decision. HHS describes two methods for meeting the Privacy Rule's de-identification standard, Expert Determination and Safe Harbor; whether either could apply to a given archive is decided in SourceX's review with the company and its counsel, never by the partner.

The person who can authorize a licensing discussion is the CEO of the party that controls the records, with the CFO or general counsel advising. The company baseline is 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Unknown until SourceX reviews it: the rights position, the de-identification required, whether the records match a dataset need and any terms. Partners sign the Channel Partner Agreement before submitting introductions.

Background for the rights questions sits in [what a business associate is](/questions/what-is-a-business-associate-hipaa), [licensing healthcare operational data without PHI](/questions/license-healthcare-operational-data-without-phi) and the [18 HIPAA identifiers](/resources/18-hipaa-identifiers). The [healthcare operations page](/industries/healthcare-operations) and the [screening worksheet for healthcare administration businesses](/resources/a-referral-screening-worksheet-for-healthcare-administration-businesses) help decide whether a client fits, and related record patterns are on the [reconciliation exceptions data page](/data-types/reconciliation-exceptions-ai-agent-training-data).

## Go deeper on appointment referral reconciliation

- [Appointment referral reconciliation exception examples](/guides/appointment-referral-reconciliation-exception-examples): a worked unmatched referral, from the original request to the closed loop.
- [Appointment referral reconciliation records across systems](/guides/appointment-referral-reconciliation-records-across-systems): a map of the IDs and mappings that join scheduling, work-queue, service desk and closure records.
- [Who can license appointment referral reconciliation records](/questions/who-can-license-appointment-referral-reconciliation-records): a short answer on whether to introduce the practice, the health system or the services company.
- [Appointment referral reconciliation referral brief template](/resources/appointment-referral-reconciliation-referral-brief-template): a fill-in brief for writing the company introduction.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a healthcare administration client is replacing its scheduling or referral platform and its exception and mapping history may not survive the cutover, [register as a partner](/register), confirm the company that controls the records against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you introduce the decision-maker.

## Sources

- https://ecqi.healthit.gov/sites/default/files/ecqm/measures/CMS50-v14.0.000-QDM.html
- https://oncprojectracking.healthit.gov/wiki/spaces/TechLab360X/pages/18776122/360X+Implementation+Guide
- https://www.hhs.gov/hipaa/for-professionals/special-topics/de-identification/index.html
- https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.html
- https://refer.sourcex.si/terms
