Revenue cycleLive · in the productMoney

AuthPilot

The pre-authorisation justification, cited and checked, on the claim — inside Claims.

Installs with ClaimsLine, whose screen it works on

Get AuthPilot Open the appAvailable nowHow pricing works →

What it is

A view inside ClaimsLine — installing it installs ClaimsLine, because the claim, its payer, its amounts and its pre-auth states are already Claims, and a second claim store would be a second answer to “what did we tell the insurer”. What this adds, on the claim that already exists, is the clinical justification itself: drawn from the record with every paragraph carrying the row it came from, and a named person who read it before it went. Open a claim on Claims and the pre-authorisation packet is under it.

Who uses it: Built for: Every specialty
Reads: The record: diagnoses, admission, results, estimate, medicines, the claim
Writes: A drafted justification, its citations, and who checked it
Never: It submits nothing.
Access: Only people whose role includes it — the clinic owner decides who
Your data: Full PHI. Hosted in Boston, United States. On uninstall: Every record stays; only the workflow leaves.

How it works

Start a packet on the claimOn a claim’s Journey, under Pre-authorisation, press Start a packet — a claim that already carries a live packet is refused a second one until that one is superseded.
Cite what the record offersThe candidates list reads the patient’s own coded diagnoses, admission, abnormal results, an active estimate and active medicines, each with the row it came from; press Cite on the ones the justification rests on, and an empty list says ‘The record has nothing to cite yet’.
Write the justificationThe textarea asks why this admission and this procedure, in the words a TPA reads; Save the justification stays disabled under 40 characters, and the assistant panel below can draft a first version for you to edit rather than write cold.
Check it — a person, not a jobI have read it is refused with no justification written and refused again if nothing has been cited; passing both, it stamps the packet checked under the name of the person who pressed it.
Mark it sentOnce checked, Mark it sent asks for the reference the insurer gave back and is refused on anything but a checked packet — nothing here submits to an insurer itself.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It submits nothing.

There is no payer connection behind it: it assembles the packet and marks it sent when a person has sent it.

It cannot be checked with an empty justification or with nothing cited, the person who checked it is the session rather than a name in a form, and nothing can be marked sent that was not checked first.

Every citation is re-read as this hospital’s own row about this very patient before it is stored.

AI in AuthPilot

AskQuestions about what is on screen — “What needs attention in AuthPilot today?” — answered with the records it read.

DraftSummaries and notes for the team, marked as drafts until a person signs.

Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

AuthPilot — Claims — Draft the pre-authorisation justification from the record, every line cited — 01Claims — Draft the pre-authorisation justification from the record, every line citedCaptured from the running demo clinic

01Claims — Draft the pre-authorisation justification from the record, every line citedCaptured from the running demo clinic

1 of 1

Questions clinics ask

What does AuthPilot do?

The pre-authorisation justification, cited and checked, on the claim — inside Claims. A view inside ClaimsLine — installing it installs ClaimsLine, because the claim, its payer, its amounts and its pre-auth states are already Claims, and a second claim store would be a second answer to “what did we tell the insurer”. What this adds, on the claim that already exists, is the clinical justification itself: drawn from the record with every paragraph carrying the row it came from, and a named person who read it before it went. Open a claim on Claims and the pre-authorisation packet is under it.

What data does AuthPilot read and write?

AuthPilot reads the record: diagnoses, admission, results, estimate, medicines, the claim and writes a drafted justification, its citations, and who checked it. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

What does AuthPilot deliberately not do?

It submits nothing. There is no payer connection behind it: it assembles the packet and marks it sent when a person has sent it. It cannot be checked with an empty justification or with nothing cited, the person who checked it is the session rather than a name in a form, and nothing can be marked sent that was not checked first. Every citation is re-read as this hospital’s own row about this very patient before it is stored.

What happens to our data if we uninstall AuthPilot?

Every record stays; only the workflow leaves.

Is AuthPilot available today?

Yes — AuthPilot is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see AuthPilot running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

More in Revenue cycle

All 39 →