AuthPilot

◦ in design

Built — inside Claims, on the claim that already exists.

Revenue cycle · Full PHI · Every specialty

What AuthPilot does

THIS IS NOT A SEPARATE APP, and the capability shipped. The claim, its payer, its amounts and its pre-auth states are Claims (ClaimsLine); the counselling side of the same admission is Admissions; and the pre-authorisation pack is already a document this product prints. A third claim store beside those would be a third answer to “what did we tell the insurer”. What was missing sat between them and is what was built: 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. Find it under Claims → Pre-authorisation.

See it on screen
No screenshot of AuthPilot yet.This app is still in design; the demo clinic shows the working clinic it will join.Open the demo clinic

What it reads

the record: diagnoses, admission, results, estimate, medicinesthe claim

What it writes

a drafted justification, its citations, and who checked it
Same patient record as every other app — nothing is copied into a silo. Data class: Full PHI.

What it does 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.

Every app page carries this section. A listing with only benefits is an advertisement.

Questions clinics ask

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?

AuthPilot is in design: the surface exists and the platform underneath is ready. Join the waitlist and it moves up the build order.

Ask about AuthPilot

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.

We use your name, phone number and clinic name for one thing: to answer this enquiry about MedAppz. It is stored on our own server, in the single region our trust centre names, and it is not sold or passed to anyone else.

Email us

You can withdraw either at any time: write to hello@medappz.com, or tell whoever calls you, and we will delete what you gave us.

More revenue cycle apps