Bonversefor clinics
01 / Bonverse for Clinics

AI agents that handle your inbound referrals, prior authorizations, and patient phone calls.

Operates on top of your athenahealth, NextGen, eClinicalWorks, Epic, payer portals, and phone lines. HIPAA-ready. No rip-and-replace. First workflow live in 5 days.

Built by engineers from Google and Uber. Deployed in partnership with practice leadership — not self-serve.

5days
To first workflow live on your EMR
900+
EMR, payer, and phone integrations
Every
Write action pauses for human approval
02 / The three workflows

Three places your front office loses the week.

We don't start with a platform pitch. We start with the three workflows every practice manager we've spoken to named as the ones their team keeps re-doing by hand.

Workflow 01

Inbound referrals into your EMR.

Twenty fax pages a day, half are referrals — each one has to land in the EMR with the right insurance, ICD-10, and routing before anyone calls the patient.

12–18hrs/week per front-office staff
Our AIReadExtractVerifySchedule
Workflow 02

Prior authorizations, end to end.

Two coordinators full-time, just chasing prior auths across six payer portals — and denials still surface six weeks later as unpaid claims.

14–20hrs/week per front-office staff
Our AISubmitTrackAppealConfirm
Workflow 03

Patient phone, scheduling, and eligibility.

After-hours calls go to voicemail. Daytime calls bottleneck the front desk. Either way, slots stay open and patients walk to a competitor that picks up.

10–16hrs/week per front-office staff
Our AIAnswerVerifyBookConfirm
03 / How it works

Three actions. In that order. Every time.

Our AI is an agent, not a chatbot. It works on the same charts, referrals, and payer portals your front office already uses — and it doesn't take a write action without a signoff.

Step 01Reads

Ingests the documents. Extracts the fields you care about.

Referral faxes, insurance cards, prior auth packets, H&Ps, imaging orders. Our AI pulls the 15–30 fields the front office cares about — patient, DOB, payer, group #, ICD-10, CPT, referring MD — and normalises them against your EMR schema.

Extracted · sample
  • patient  → Maria Hernandez · 04/22/1978
  • payer    → Aetna PPO
  • group    → 0834-A
  • icd_10  → M54.5 (low back pain)
  • ref_md  → Dr. Liu (Sunset PCP)
Step 02Reconciles

Cross-checks against your EMR and eligibility. Drafts the next action.

Our AI reconciles the extracted data against your live chart and real-time payer eligibility, flags mismatches in plain language, and drafts the next move — the EMR appointment, the prior auth packet, the patient callback.

Flags · 2 of 14 fields
  • !!eligibility Aetna PPO active; copay $40 not on file.
  • !!icd_10 missing on referral; M54.5 inferred from H&P.
Step 03Pauses for approval

Waits for a human. Nothing posts without signoff.

For every write action — an EMR appointment, a prior auth submission, a patient SMS — our AI stops and waits. Your front office decides what goes out, and when.

Pending · awaits approval
Submit prior auth to BCBS — case CASE-204515
12 fields ready · 1 flag cleared · est. payer turnaround 48 hr
APPROVEEDITROLLBACK

Our AI drafts; your team approves. Humans stay in the loop on every write action.

04 / Why practices trust Bonverse

An architecture built for practices that can't afford PHI mistakes.

Healthcare is unforgiving. A wrong CPT is a denied claim; a leaked portal login is an OCR investigation. We designed our AI with that in mind from the first line of code.

Principle 01

Credentials and PHI never touch the model.

Your EMR and payer portal logins stay in a secure vault. The model never sees them. Our AI operates through a proxy that authenticates separately and redacts PHI before any LLM call — so the model only sees the task, never the keys or the chart.

Principle 02

Approval gates on every write.

Nothing posts to your EMR or a payer portal without a human signoff. Once your front office trusts the pattern, approval gates are configurable per workflow — not an all-or-nothing switch.

Principle 03

HIPAA-ready audit trail, exportable.

Every action our AI takes is logged with inputs, reasoning, and outputs. Pull the trail as CSV or PDF for compliance reviews, payer audits, or when a patient asks what happened on their referral six weeks ago. BAA on request.

05 / Integrations

Works where your team already works.

Our AI is EMR-agnostic. It connects to the systems your front office already has open — your EMR, the payer portals they log into for every auth, and the phone, fax, and inbox where patients and referrals come in.

EMR
Practice management
athenahealth
NextGen
eClinicalWorks
Oracle Health
Epic
DrChrono
Payers
Eligibility & prior auth
Availity
Change Healthcare
Waystar
Office Ally
CoverMyMeds
Phone, fax & inbox
Patient communication
Twilio
RingCentral
Spruce
Outlook
Gmail

If your practice uses it, we probably connect to it — 900+ integrations supported.

06 / Deployment

From first call to live, in under a fortnight.

We don't run four-week discovery phases. We map your actual process, configure our AI to it, and run real referrals in shadow mode before anything goes live.

Days 1–2

Workflow map

A 30-minute call with your practice manager. No deck, no slideware — we walk your actual process, fax by fax, call by call.

Days 3–5

Configure on your process

We stand our AI up on your stack using anonymised samples you supply. Your EMR fields, your payer mix, your scheduling rules.

Days 6–7

Shadow mode

You run our AI alongside your front office on 5–10 real referrals or calls. Nothing posts anywhere. You compare drafts to what your team would have done.

Day 8+

Go live

Live, with human approval gates on every action for the first two weeks. Loosen the gates per workflow, on your timing, never ours.

07 / Questions we get

The things practice managers ask on the first call.

If yours isn't here, write to us. We keep the first email short.

01Will this break my EMR?+
No. Our AI operates on top of your EMR through the same interfaces your front office already uses. We don't touch the schema, we don't install anything inside it, and nothing posts without an approval you control.
02Is this HIPAA compliant?+
Yes. PHI is encrypted in transit and at rest, credentials never touch the model, and PHI is redacted before any LLM call. We sign a BAA and store data in the region of your choice. Every action is logged and exportable for OCR-ready audit trails.
03What if the AI makes a mistake?+
Approval gates mean a human signs off every write. If something gets through that shouldn't have, the audit trail shows exactly what our AI did, why, and with what inputs — and you can roll back the action in one click.
04Can I start with one workflow?+
Yes — we recommend it. Pick the one costing your front office the most hours this month — usually inbound referrals or prior auths. We go live on it in 5 days, and you add the next one when you're ready.
05What if I use an EMR you don't list?+
If it has an API or a web UI, we can almost certainly connect to it. We've worked with athenahealth, NextGen, eClinicalWorks, Epic, Oracle Health, DrChrono, and several smaller systems. Email us with your EMR name and we'll confirm within 24 hours.
06Who built this?+
A small team of engineers who've shipped production systems at Google and Uber, working alongside practice managers in our pilot clinics. We pair with your leadership on every deployment — so the humans configuring our AI are the same ones you'll talk to when something needs to change.
08 / Write to us

If referrals, prior auths, or patient calls are eating your front office's week — write to us.

Tell us which of the three workflows is costing your front office the most hours — we'll reply with what the first week would look like on your EMR.