Every dispense, every claim, every purchase, every rebate as a unified record that empowers your team to capture what was already earned.
ILLUSTRATIVE · SAMPLE DATA
A patient sees their provider. A prescription is written and filled. An administrator confirms it qualifies. The drug is replenished at the discounted price. The benefit is realized. For most of the program's life, that was the whole of it. Until it wasn't.
A prescriber who was never enrolled generates no alert. A refill that moves out of network generates no exception. A qualified claim replenished at full price creates no notification. A rebate never submitted produces no denial.
They all go unnoticed for the same reason: no single system manages the whole record.
Every one that happened. Not only the ones that were claimed.
What qualified, what didn't, and exactly which rule decided.
Matched to the dispense it replenished, at the price in effect.
Filed inside the window, checked against what it should have paid.
This is 340B revenue cycle management,
and the record that's needed to support it.
Medical billing has a charge master — a record of every service that should generate a claim. 340B has never had one. Proximity builds it, organized around the patient and assembled independently of what was submitted, so you can see which interactions should have produced claims at all.
Every program has a disqualification queue, and the assumption is that the rejections are correct. Some are. Others failed on a data quality problem, or a rule applied to an incomplete record. In the queue they look identical — same status, same reason code, different truth. We re-run both directions against the complete record, and show which rule decided.
Until now a missed 340B dollar stayed missable — findable in March, still recoverable. From January 2027 a rebate-eligible dispense has a window, and its filing is routed by a rule the manufacturer sets, not you — per NDC, inside a single manufacturer's portfolio. None of it is in your claim data. Miss either and nothing errors; the money is gone, not deferred. Where your contracts let us file, we file. Where they don't, we track every filing and flag what never went.
A claim can pass every check — administrator, submission platform, wholesaler — and still be replenished at full price. Nothing generates an alert, because no system compares your qualified claims against your wholesaler invoices. We do, at the level of the individual product, pharmacy and date.
Two rebate programs now reach the same drugs, and the lower price governs, so they cannot both pay. Telling a Maximum Fair Price dollar from a 340B dollar takes the purchase record, and no administrator holds one. We compute what each dispense was owed, then reconcile both programs against one ledger.
ILLUSTRATIVE · SAMPLE DATA
You are accountable in an audit. Not your vendor. Every conclusion is deterministic — same inputs, same finding, from stated rules rather than inference — and each traces back to the rule, the reference data, and the records it ran against. Models help author rules. They do not produce conclusions.
You are not asked to export files, reconcile formats, or upload anything. We submit what you direct, to destinations you name. We do not sell, license, or share your dispense-level data with manufacturers, pharmacy benefit managers, or their agents — there is no second customer for it.
Your program is the financial foundation of your mission. Start with the gap we can quantify from public data, before you give us access to anything: registered sites operating without their own contract pharmacies.
In-house dispensing, mixed use, and contract pharmacy are almost never measured together. Start with the check almost nobody has run: your wholesaler invoices against your qualified claims.
That instrument has never existed.
We built it.
Proximity works on 340B and nothing else. One program, at a depth that is only possible if it is the only thing you build for.