Referral operations for infusion centers
Every referral, every team, one shared path to treatment.
InfuseStack runs the work between a referral arriving and a patient being ready to schedule: benefit investigation, clinical review, verification and authorization, as one workflow your teams share, reading directly from the system you already run.
The problem
One referral crosses every team in the building.
Work waits between teams
Benefits, clinical, verification and authorization each hold part of the answer. When the hand-off is an email, the referral sits until someone notices.
Nobody can see what it is waiting on
A referral is one patient, one drug and one payer, with work spread across people who share no screen and no list.
Leaders cannot find the slow step
Without a shared record of the work, there is no way to say which step, payer or site is holding treatment back.
Referral workflow
Parallel where the work allows it. Gated where it must be.
Intake reviews the referral first. Then benefit investigation and clinical review start together. Verification begins only when both have succeeded, and authorization follows. Steps carry their own checklists and due dates, and every action is recorded.
Intake review
Is it a referral we can treat, and is it complete?
At the same time
Benefit investigation
Coverage, benefits and cost share
Clinical review
The order, diagnosis and documents
Verification
Starts only when both have succeeded
Authorization
Tracked through to the payer's decision
Ready to schedule
Every gate cleared
Queues first, then people
Work routes to the owning team's queue, where anyone on the team can take it, so nothing waits in the inbox of someone who is away.
Requests between teams
Benefits can ask patient communication to reach a patient; clinical can ask provider communication for missing information from the referring office. The answer returns as follow-up work for the team that asked.
Checklists that gate the outcome
A result that requires a checklist cannot be recorded without it. The rule is enforced when the work is submitted, not only shown on screen.
A history that is never rewritten
Every action on a referral is recorded in order and never edited, so anyone can see what happened, who did it and why.
Beyond the workflow
The context behind each decision, next to the work.
Coverage requirements, drug economics and site performance come from the same records your teams work from, so the numbers and the work never disagree.
What each payer requires
For a drug and a payer, InfuseStack shows the steps a referral must clear before treatment. Requirements learned from your own history stay advisory until a published payer policy confirms them, and staff can override with a reason.
Drug pricing you can trace
WAC, NADAC and Medicare Part B payment limits converted to billing units, each labeled as published, derived or estimated and linked to its public source. Add your own acquisition, GPO and 340B prices on top.
How each site performs
Compare locations on throughput, speed to treatment, cancellations and purchasing side by side, with utilization measured against the days each site is open.
A report leadership can check
Denials by category, time from order to treatment, and drug margin against Medicare benchmarks, computed from your data. Any written summary is checked figure by figure against those numbers before anyone reads it.
Security
Designed around protected health information.
Patient data is read where it lives, touched by as little of the system as possible, and every access is attributable to a person.
Your EHR stays the system of record
InfuseStack reads what it needs from your EHR and writes nothing back. Reads pass through a signed gateway that accepts reads only.
Access you can account for
Every read of patient information is recorded with who performed it. Support access is read-only, requires a stated reason and is logged.
Single sign-on
SAML single sign-on for each organization, with domain verification. Roles are granted inside InfuseStack, never by an identity provider.
Separated by customer
Each customer's connection is sealed with its own key, and every query is scoped to the organization that owns the data.
See how your referrals would move.
Tell us about your center: your teams, your payers and the EHR you run. We will walk you through InfuseStack.