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
| System | Record | Linking key | Usual owner |
|---|---|---|---|
| Referral intake or EHR referral module | Referral request with intended service, location code, priority and status history | Referral ID (primary key) | Administration or patient access director |
| Scheduling platform | Appointments, reschedules, cancellations, no-shows; resource tables | Referral ID if the workflow passes it; resource and location codes | Administration director, with the applications lead |
| Service desk | Tickets and change requests for mapping fixes | Ticket number; referral ID only if someone typed it | IT service desk manager |
| Report delivery (interface inbox, document store, fax server) | The returned report or procedure note | Sometimes the referral ID; otherwise patient and date | Health 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.
Dated mappings: the link most often lost
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 field | Why it matters | Usual home |
|---|---|---|
| Location code | What the referrer chose | Referral form options |
| Bookable resource | What scheduling could fill | Scheduling resource table |
| Effective from and to | Which meaning applied on the referral's date | Resource table history, if kept |
| Change ticket and approver | Who changed the meaning and why | Service 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.
| Step | System | Record | Carries |
|---|---|---|---|
| 1 | Referral intake | Request for an MRI at location code WEST-2 | Referral ID R-40217 |
| 2 | Scheduling | Unmatched: WEST-2 has no MRI resource after March 1 | R-40217 and resource code |
| 3 | Service desk | Ticket SD-1182: WEST-2 MRI retired, map to CENTRAL-1 | Location codes; approver and date |
| 4 | Scheduling configuration | WEST-2 MRI effective to February 28; CENTRAL-1 effective from March 1 | Effective dates; SD-1182 |
| 5 | Scheduling | Appointment booked at CENTRAL-1 | R-40217 |
| 6 | Report delivery | Radiology report received by interface | R-40217 |
| 7 | Referral intake | Status closed, evidence attached | R-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.