Referral reconciliation system map: the referral ID and dated mappings that join four systems

Short answer

Two things rebuild a referral across systems: a referral ID that survives every hop, from request to appointment to ticket to returned report, and location and provider mappings kept with their effective dates. With both, the referral intake, the scheduling platform, the service desk and the report inbox can be stitched into one case. Without them, matching depends on patient details, which a de-identified history cannot use.

Visual briefFull-size diagram
Four system nodes in a row (referral intake, scheduling platform, service desk, report delivery) with the referral ID token travelling along the connectors and a dated mapping table below, joining one referral into a single case.
Illustrative. Which identifiers survive depends on each company's systems, configuration and contracts.

This system map is part of the appointment referral reconciliation guide. The guide covers what to inventory before a platform migration; this page shows which system holds each record, which identifier links it onward and what one fully joined referral looks like.

Four systems, one referral

SystemRecordLinking keyUsual owner
Referral intake or EHR referral moduleReferral request with intended service, location code, priority and status historyReferral ID (primary key)Administration or patient access director
Scheduling platformAppointments, reschedules, cancellations, no-shows; resource tablesReferral ID if the workflow passes it; resource and location codesAdministration director, with the applications lead
Service deskTickets and change requests for mapping fixesTicket number; referral ID only if someone typed itIT service desk manager
Report delivery (interface inbox, document store, fax server)The returned report or procedure noteSometimes the referral ID; otherwise patient and dateHealth information manager

Four systems usually means four owners, four retention schedules and four separate decisions in a migration plan.

The referral ID: the one key that must survive

Every join in the map runs through the referral ID. Standards show what a well-joined workflow looks like. ONC's 360X closed-loop referral guide ties the request, the acceptance or decline and the result of referral together with a unique referral ID, so the returned note can be matched to the request that asked for it. In HL7 FHIR R4, an Appointment can point to the ServiceRequest it is allocated to assess through its basedOn element, and a ServiceRequest carries its own identifiers. A company does not need to use either standard. The question is whether its own systems keep an equivalent link.

Where it breaks:

  • Scheduling. The appointment carries the referral ID only if the intake workflow passes it. A scheduler who books from a phone call may create an appointment with no link at all.
  • Service desk. The ID appears in a ticket only if a person types it. Mapping tickets usually cite a location code, not a referral.
  • Report delivery. Returned reports may arrive by interface, with the ID, or by fax, without it.

CMS's Closing the Referral Loop measure (CMS50) counts referrals for which the referring clinician receives the report back. A company that can show that match by referral ID, rather than by patient name, holds a closure record that can survive de-identification.

The second link is less obvious. A location code like "East" means one thing in March and another in May, after the service moves. A migration usually loads the current location and provider list, not the history of what each code meant in a given month. An old referral addressed to East can then look like an error rather than a reasonable request made before the move.

Mapping fieldWhy it mattersUsual home
Location codeWhat the referrer choseReferral form options
Bookable resourceWhat scheduling could fillScheduling resource table
Effective from and toWhich meaning applied on the referral's dateResource table history, if kept
Change ticket and approverWho changed the meaning and whyService desk

Ask whether historical mappings, with effective dates, will be kept.

One fully joined referral (Illustrative)

Invented for this page. A fictional 280-person imaging and diagnostics management company. Every identifier is made up and shows the shape of the chain, not a real record.

StepSystemRecordCarries
1Referral intakeRequest for an MRI at location code WEST-2Referral ID R-40217
2SchedulingUnmatched: WEST-2 has no MRI resource after March 1R-40217 and resource code
3Service deskTicket SD-1182: WEST-2 MRI retired, map to CENTRAL-1Location codes; approver and date
4Scheduling configurationWEST-2 MRI effective to February 28; CENTRAL-1 effective from March 1Effective dates; SD-1182
5SchedulingAppointment booked at CENTRAL-1R-40217
6Report deliveryRadiology report received by interfaceR-40217
7Referral intakeStatus closed, evidence attachedR-40217

Steps 1, 2, 5, 6 and 7 join on R-40217. Steps 3 and 4 join on the ticket number and the effective dates. Without step 4, step 2 looks like a scheduler's mistake. Without R-40217 on step 6, closure depends on patient details. The worked unmatched referral shows the same chain from the people involved.

Questions that test the map, at metadata level

Ask the administration director and applications lead, without opening a referral:

  • Does every appointment created from a referral carry the referral ID?
  • Do returned reports arrive with the referral ID, and what share come by fax?
  • Are location and provider mappings kept with effective dates, and will that history migrate?
  • Do mapping tickets name an approver?
  • Which systems go read-only or dark at the migration, and on what date?

Whether a particular referral module, scheduling platform or service desk exports status histories, reason codes or change records depends on the product, configuration and contract; the company confirms that with its vendors. Never collect exports, screenshots or logins.

Referral records carry patient information, so the company's contracts and SourceX's review decide what could be licensed. For SourceX, an introduced company needs 50+ full-time employees at peak (contractors excluded), a 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. The same join problem appears in finance, where general ledger reconciliation and reconciliation exceptions depend on keys surviving between systems; in distressed situations, recovering value from company records raises it again. The referral brief template records your answers.

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 client's referrals still carry one ID from request to returned report, and its mapping history is dated, register as a partner, check the company against who qualifies and read the program terms before you introduce its decision-maker.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Why not match referrals on patient name and date of birth instead of a referral ID?

Because a de-identified history cannot use those fields. If the only way to join a request to its appointment and report is through patient details, the join disappears the moment those details are removed.

Should a partner tell the client what their platform can export?

No. Export capability depends on the product, the configuration and the contract. The company confirms it with its vendors; a partner asks the question and records the answer.

Sources

  1. oncprojectracking.healthit.gov/wiki/spaces/TechLab360X/pages/18776122/360X+…
  2. hl7.org/fhir/R4/appointment-definitions.html
  3. hl7.org/fhir/R4/servicerequest.html
  4. ecqi.healthit.gov/sites/default/files/ecqm/measures/CMS50-v14.…
  5. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment