Unmatched referral worked case: a sleep study sent to a lab that had moved

Short answer

The records that explain a referral exception are the referral request as submitted, the unmatched-queue entry with its reason code, the service desk ticket and approved mapping change that fixed the cause, the rebooked scheduling event carrying the original referral ID, and the returned report that closed the loop. In the Illustrative case below, a sleep study was sent to a site that had moved. Seven dated records, made by five different people, tell the whole story.

Visual briefFull-size diagram
A vertical case timeline from Day 0 to Day 24 that branches at Day 2, when the referral to the East site cannot be matched, then runs through a service desk ticket, a mapping change, rebooking at North, the visit and the returned report that closes the loop.
Illustrative case at a fictional healthcare management services company. No patient data is shown.

This worked case is part of the appointment referral reconciliation guide, which covers what to inventory before an administrative platform migration. Here we follow one referral from request to closure and finish with how a healthcare workflow advisor can spot similar cases at a client. This page is general information, not legal or compliance advice.

What went wrong with the East referral (Illustrative)

Invented for this page. A fictional 450-person healthcare management services company runs central scheduling and referral intake for 30 affiliated practices. A primary care practice refers a patient for a sleep study at the "East" location.

The East sleep lab closed two months earlier when the service moved to the "North" clinic. Nobody removed East from the referral form. The form still offered it, accepted the request and passed it to scheduling, where nothing could be booked.

Nothing here is unusual. Services move, forms lag, and a request can be valid when written and still impossible to fill. What makes the case useful is that each person who touched it left a record.

The referral, day by day

The table is this page's evidence asset: when, who decided, what they decided and the record that holds it.

DayWho decidedDecisionRecord it leftSystem
0Referring clinicianRequest a routine sleep study at EastReferral request with service, location code and priorityReferral intake
2SchedulerCannot book; move to unmatched queueQueue entry, reason "location has no schedulable resource"Scheduling work queue
3Intake leadReport that the East code still appears after the moveService desk ticketService desk
5Applications team, with named approverRetire the East sleep code and map it to NorthMapping change, approver and date on the ticketScheduling configuration and service desk
6SchedulerContact the patient; book at NorthScheduling event carrying the original referral IDScheduling platform
19Sleep physicianPerform the studyVisit completedScheduling platform
24IntakeMark the referral closed once the report arrivesClosure flag with the report as evidenceReferral intake and document store

Two identifiers hold the chain together. The original referral ID travels from Day 0 to Day 24, and the ticket number links the Day 3 report to the Day 5 change. Lose either and the story breaks into unrelated records.

Why the closure on Day 24 matters most

A referral history without closures is a history of requests. Day 24 is what turns it into a history of outcomes, and it has a standard meaning.

CMS's eCQM, Closing the Referral Loop (CMS50), counts referrals for which the referring clinician receives a report back from the clinician the patient was sent to, and in version 14 of the measure a procedural report can satisfy it. ONC's 360X implementation guide describes the same cycle as messages: a referral request, an acceptance or decline, and a result of referral that closes the loop, tied together by a unique referral ID. The case above follows that cycle informally, which is common in companies that never implemented 360X. The sequence still holds.

Read in order, the seven records teach three things an AI agent working in scheduling would need to learn:

  1. A valid request can be unmatchable. The Day 0 request was not wrong; the configuration was out of date.
  2. The fix is a configuration change with an approver. Day 5 is not a workaround by one scheduler. It is a change with a name and a date.
  3. The referral is not done until the report returns. Day 19 is a visit; Day 24 is the closure.

The same "unmatched item, explanation, sign-off" shape appears in finance, where reconciliation break notes and close checklists record it. The general argument is in exception handling records for AI agents.

What a partner can take from this case

A partner needs none of these records to recognize the pattern. The case is a reason to ask about record classes, not a request for any referral.

Referral records carry patient information. HHS guidance says a business associate contract must set out the business associate's permitted uses and disclosures of protected health information and cannot authorize a use the covered entity itself could not make. A management services company running intake for practices may therefore need its practices' agreement, or may only be able to discuss operational data that is not patient information. That is decided by the company, its counsel and SourceX's review, never by the partner. The who-can-license decision tree maps the path.

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. Whether any record class can be licensed, in what form and with what buyer interest stays unknown until SourceX reviews it. Partners sign the Channel Partner Agreement before submitting introductions.

How to spot similar cases at a client

Healthcare workflow advisors see the signs during intake redesigns and platform projects. Without opening a referral, ask the administration director:

  • Have locations, services or providers moved in the last few years? Each move can strand referrals addressed to the old site.
  • Is there an unmatched or exception queue, and does it carry reason codes?
  • When a mapping changes, is there a ticket with an approver?
  • Does the rebooked appointment keep the original referral ID? The system map for referral records shows why that one field matters.
  • How is closure recorded: a flag, a returned report or both?
  • Is the scheduling or referral platform being replaced, and when does legacy access end?

Healthcare operations gives wider sector context.

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 can follow an unmatched referral like this from request to returned report, register as a partner, check the company that controls the records against who qualifies and read the program terms before introducing 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

Is a referral that was eventually booked still an exception worth noting?

Yes. The useful part is not the booking but the path to it: why the request could not be matched, who changed what, who approved it and how the loop closed. A referral booked first time leaves none of that.

Does this case need patient details to be useful?

No. The sequence of statuses, reason codes, tickets and closure evidence carries the lesson. Whether patient information could be removed, and under which method, is decided in SourceX's review with the company and its counsel.

Sources

  1. ecqi.healthit.gov/sites/default/files/ecqm/measures/CMS50-v14.…
  2. oncprojectracking.healthit.gov/wiki/spaces/TechLab360X/pages/18776122/360X+…
  3. hhs.gov/hipaa/for-professionals/privacy/guidance/bus…
  4. 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