340B Referral Capture: How to Recover the Prescriptions Your TPA Is Missing

340B referral capture is the process of finding prescriptions your TPA marked ineligible because an outside specialist wrote them, then proving from the medical record that your covered entity still managed the patient's care. For most covered entities, it is the largest pool of legitimate, recoverable savings sitting inside the ineligible-claims report, and almost nobody reviews it.

Every TPA running a 340B program asks four questions about each claim: is this an eligible patient, an eligible provider, an eligible location, and the right window of time? If any one answer is unknown, the claim is excluded. No flag for later review. No pharmacist pulls the chart. The claim simply drops out, and the covered entity never sees it again.

Referral prescriptions are where this logic breaks most often. Your provider refers a patient to a cardiologist down the street. The cardiologist writes a prescription. The patient fills it at your contract pharmacy. Nothing in that story makes the claim ineligible, but the prescriber's NPI is not on your provider list, so the TPA buckets it with claims that truly should be excluded.

This guide covers what referral capture is, why TPAs cannot catch it on their own, the documentation standard HRSA holds you to, how to size the opportunity, and how to build a program that holds up in an audit.

Key takeaways

• Where the prescription was written does not decide eligibility. Who is responsible for the patient's care does.
• TPAs match rosters and locations; they cannot read consult notes. Referral capture always needs a human documentation review.
• Four documentation elements must exist in the record at the time of care, not be built afterward.
• Start sizing the opportunity from the ineligible-claims report you already receive.
• Audit your own referral captures every quarter.

What is 340B referral capture?

340B referral capture means identifying prescriptions written by a provider outside the covered entity, confirming the covered entity kept clinical responsibility for that patient, documenting it, and claiming the 340B discount the TPA excluded by default.

The scenario repeats almost everywhere. A patient is registered with a federally qualified health center, a Ryan White clinic, or a hospital outpatient department. A provider employed by or contracted with the covered entity treats them and makes a specialist referral to dermatology, cardiology, or behavioral health. The specialist is not on the covered entity's 340B roster and may not belong to the same health system. The patient then fills the specialist's prescription at the pharmacy they have used for years.

HRSA's 1996 patient definition guidance is clear that eligibility does not depend on where the prescription was written. It depends on whether the covered entity maintains responsibility for the patient's care, including when services are provided under a referral arrangement. The prescribing site can be outside your walls. The clinical relationship cannot.

That single distinction is the whole referral prescription capture opportunity, and it is exactly what TPA software is not built to examine.

Why TPA qualification logic misses referral prescriptions

TPA qualification logic is a checklist, not a clinical review. It runs each claim against three lists: prescriber NPI against approved providers, dispensing location against approved sites, and date of service against an eligibility window. That is fast, and it is right for the vast majority of claims. If you want to understand how 340B eligibility works at the claim level, this matching step is the core of it.

What the engine cannot see is the chart. It does not know that Dr. Ramirez at an outside cardiology group wrote this prescription because Dr. Patel at your clinic sent a referral three weeks earlier, received the consult note, and kept managing the patient afterward. Without that context, the TPA marks the claim ineligible and files it away.

Multiply that by every specialist, every outside lab, and every ED visit that produced a prescription. The ineligible-claims report becomes a graveyard of valid claims nobody went back to defend. This is also why an independent look at your TPA qualification logic often surfaces referral gaps first.

Referral capture is a documentation exercise, not a technology fix. Software can surface candidates faster. A person still has to line up the encounter note, the referral order, and the consult note, and confirm the story holds from start to finish. Programs that treat it as a software checkbox either capture almost nothing or capture too aggressively and draw audit findings.

What documentation does 340B referral capture require?

340B referral capture requires four documentation elements, all found in the medical record at the time of care: a qualifying encounter, a referral order, a returned consult note, and evidence of continuing care. HRSA does not ask where the prescription was written. It asks whether you can show, with contemporaneous records, that your covered entity never stopped being responsible for the patient.

This is the documentation standard every audit-ready program is built on, and it is the practical answer to how to document 340B referral capture.

1. A qualifying encounter. The patient was seen at a 340B-registered site by a provider employed by, or under a qualifying contract with, the covered entity. No eligible encounter, no eligible referral.
2. A documented referral order. The eligible provider's note records who the patient was referred to and why. This is the closed-loop referral auditors want to see, not a patient who found a specialist on their own.
3. A closed-loop consult note. The specialist's note comes back into your record and names the patient, the diagnosis or reason for referral, and the specialty. Be specific: auditors have flagged files that pointed to the wrong department's note when two specialties shared a records system.
4. Continuity of care after the referral. Your provider remains the provider of record for ongoing management. This shows the relationship lasted beyond one appointment.

When all four are present and filed, the referral prescription is a defensible 340B claim. When one is missing or ambiguous, the claim is a liability that tends to surface in the next HRSA audit or manufacturer diversion review. Referral files are among the areas HRSA examines most closely.

A capture program without reliable medical record access and complete files is not a capture program. It is a repayment program waiting to happen.

How much revenue does referral capture recover?

How much revenue referral capture recovers depends on your patient population, specialty referral volume, and how disciplined your current program is. Treat any single number quoted online with caution. The reliable way to size it is from your own ineligible-claims report.

Here is a sizing exercise you can run this month:

1. Pull every claim marked ineligible in the last 12 months.
2. Remove claims excluded for non-referral reasons: drug type, non-covered payer, duplicate discount risk, or out-of-window fills.
3. Keep the claims written by prescribers not on your roster. This is your referral candidate pool.
4. Pull a sample of 25 to 50 charts and check them against the four documentation elements.
5. Apply the pass rate from the sample to the full pool to estimate recoverable claims.

Not every candidate will qualify once you open the chart. Covered entities running this for the first time are usually surprised how many trace back to a legitimate referral that the TPA simply could not recognize.

What is a realistic 340B capture rate benchmark?

There is no universal capture rate benchmark for referrals. Consultants and vendors often say outside-referral prescriptions make up a meaningful share of ineligible volume, sometimes enough to change annual 340B savings. The real figure swings too much by specialty mix and geography to apply blindly.

A better benchmark is internal. Measure your referral volume, estimate how many referred patients already fill at your contract pharmacy, and track your 340B capture rate before and after launching a referral review. Two or three quarters of that comparison tells you more than any industry average.

How to increase 340B capture rate without adding audit risk

The way to increase 340B capture rate safely is to build a few repeatable habits around documentation, not to buy a single tool. These five steps separate programs that survive an audit from programs that do not.

1. Use the ineligible-claims report as your source of truth. Your TPA or 340B referral capture services vendor should send a complete, regular list of claims excluded for referral-related reasons.
2. Build medical record access into the workflow. Reviewers should pull the encounter note, referral order, and consult note in minutes, without chasing other departments.
3. Write the policy before capturing a single claim. HRSA expects written policies and procedures that define continuity of care for referrals, not an informal understanding between staff.
4. Train the people closest to the referral. Front desk staff, referral coordinators, and specialty schedulers know a specialist referral happened long before it shows up as a pharmacy claim.
5. Audit your own captures every quarter. Spot-check a sample, confirm all four elements, and fix gaps early. A mock audit or our free audit readiness scorecard is a good starting point.

Where referral capture programs go wrong

Mistake 1: inconsistency. The most common failure is not bad intent. A team documents referral claims carefully for a few months. Then staff turnover hits the referral coordinator role, consult-note review quietly slips, and six months later part of the captured claims have no specialist note behind them.

Mistake 2: treating site of service as provider of record. HRSA treats these as different tests. A patient can be seen at an eligible location without the covered entity taking on ongoing care, such as a one-time walk-in visit for an acute issue. Capturing referrals for patients you never truly managed is a classic audit finding.

Mistake 3: handing the whole judgment call to a vendor's algorithm. Automated tools are useful for surfacing candidates faster than manual review. The final call on continuity of care still belongs to the covered entity. When evaluating 340B referral capture services, ask how the tool finds candidates and who signs off on documentation before a claim is captured. Working with an independent reviewer that has no stake in the TPA or pharmacy helps keep that judgment honest.

If you are unsure how your files would hold up, review how to prepare for an HRSA audit before expanding your referral program.

Conclusion: recover what was already yours

Referral prescriptions sit in an awkward spot: too clinically nuanced for a TPA to catch, too easy to ignore in the ineligible pile, and too valuable to leave behind. The fix is a documented process built on the four elements HRSA already expects, applied consistently, audited on a schedule, and owned by people who understand both the chart and the compliance standard. Done well, 340B referral capture is less about chasing an aggressive number and more about not losing savings that were legitimately yours.

Juris 340B Solutions helps covered entities build referral capture into a broader 340B compliance program, from candidate review to audit-ready files. See our case studies or talk to our team about sizing your referral opportunity.

Sources

• HRSA Office of Pharmacy Affairs, 340B Drug Pricing Program: https://www.hrsa.gov/opa
• HRSA, Notice Regarding Section 602 of the Veterans Health Care Act of 1992, Patient and Entity Eligibility, 61 Fed. Reg. 55156 (Oct. 24, 1996)
• 340B Prime Vendor Program (Apexus): https://www.340bpvp.com