340B Prescription-to-Encounter Match
Match each prescription to an eligible encounter under a covered entity's own look-back, registered-site and referral policies.
Open the tool → Runs in your browser. Data leaves only if you deliberately send a problem report from the interactive tool.
Example
- Entity policy
- Critical access hospital; 30-day look-back; referrals do not count
- Prescription rows
- Two prescriptions with eligible encounters; one drug is orphan designated
Result: 1 of 2 prescriptions matched (50%); the orphan-designated drug was excluded for this entity type.
Answer the questions this way to reach that result. Your own answers give your own.
Inputs and output
- What you enter
Four CSV or TSV files: prescriptions with patient reference, prescriber NPI, NDC, fill date, pharmacy and orphan-designation status; encounters with patient reference, date, location and provider NPI; eligible prescribers with relationship; and registered sites. Also enter the entity type, look-back days and referral policy.
- What you get
- Eligible and ineligible prescriptions with reasons and matched encounter details, match rates by pharmacy and prescriber, and full or patient-redacted CSV downloads.
What this is
Every prescription receives an eligibility decision and the first rule it failed.
When to use it
Use this to produce a local audit trail from the entity's prescription, encounter, eligible-prescriber and registered-site files. The files remain in the browser tab.
How this is calculated
Citation
HRSA patient eligibility notice (61 FR 55156): the covered entity keeps records and retains responsibility for care delivered by its professionals or under an arrangement; 42 U.S.C. 256b(e): the orphan-drug exclusion for specified entity types. Read the source ↗
A reference and educational tool. Not medical, legal, or financial advice, and not a substitute for clinician judgment.