FeaturesPrior auth

The denial is prevented in the room.

An X12 278 has no field for the clinical note. Prior authorization is won by documenting the requirement while the patient is still in front of you — then tracking the paper until it is a certification number on the claim.

In-visit gateOrders checked against this patient’s coverage

One trackerMeds and procedures on the same worklist

Human filesCalls and filings stay with a person

Screenshots are the synthetic demo. No real patients.

The Prior auth workspace: record a certification, then a live table of requests with status, patient, CPT, payer and certification number. — Reports → Prior auth: Needs office, With payer, Approved, Denied, Expiring, with letters, appeals, pharmacy hand-off and patient texts. From the synthetic demo at demo.chartvoyant.com — no real patients.

Billing with A/R tiles and an open claim — where a missing certification number becomes a denial instead of a mystery. — The certification rides the 837. Stedi is the clearinghouse for recording the cert; it does not carry 278s. From the synthetic demo at demo.chartvoyant.com — no real patients.

How it runs

01Check coverageEvery order is tested against the plan on the chart.
02Assemble the packetThe note, the diagnosis, and the care already tried.
03A person sendsAppeals and renewals can be drafted. Filing stays human.

What it is

Forty authorizations a week, mostly by phone, is still the shape of independent specialty practice. ChartVoyant’s version is not a fax bot. Every order and prescription is checked against the patient’s coverage. When an authorization is required, the packet is assembled from the chart that already exists — the note, the diagnosis, the failed conservative care — and a person sends it.

On the clinic floor

Self-pay charts stay off the PA list. A chart with no verified insurance is on it, marked. Status texts to the patient are on by default in Admin → Reminders. Surgery Scheduling, when the office turns the module on, sends prior auth from the case Auth tab. Manual send exists on Reports → Prior auth for the packet that does not fit the happy path.

The AI biller’s hourly pass can pre-fill PA forms and draft appeals and renewals. It does not transmit an X12 278 to a payer; that submit stays synthetic. A person records a portal, fax, or phone filing. There is an Ask the AI biller line on the page. Admin → Billing → AI biller is the switch. Calls and filings stay human.

What AI does, and what a person confirms

AI drafts the packet from the attested note. It does not invent a diagnosis to satisfy a payer rule. A clinician reviews what will be sent. A denial lesson is stored so the next packet documents the cited gap instead of repeating it. That is the opposite of an autonomous prior-auth vendor that submits on a confidence score.

Non-Device CDS

Coverage rules and packet drafts are administrative. They are not a treatment recommendation. If a suggestion looks clinical — “document X to justify Y” — it is still a draft for the clinician who already decided to treat.

Where this sits vs bolted-on tools

Most PA products start from a reconstructed claim and a blank PDF. ChartVoyant starts from the visit that just happened.

Open the tracker

The synthetic demo has a prior-auth worklist. Click a row. See what was assembled from the chart.

Try the live demo Book a walkthrough

Keep reading

Orders and results stay on a timelinePA is an order-time problem. The claim should leave with the visitThe cert number has to ride the 837. Insight: the denial is prevented in the roomWhy an X12 278 has no field for the note.