Security
What happens to PHI.
Your compliance lead will ask exactly where patient data goes. Here's the full path, from the chart on screen to the suggestion in the margin. If something isn't on this page, we don't claim it.
The data path
Four steps, start to finish.
Reads the open chart
The extension reads the note, order, and payer on the page you're viewing. Nothing else in your EHR.
Strips identifiers
Names, dates of birth, MRNs, and other identifiers are removed before the note is reviewed.
Checks payer policy
The de-identified note is compared with the payer's published criteria for that procedure.
Shows suggestions
Flags appear next to your text with the policy cited. Your note only changes if you accept.
It never crawls your EHR.
No background pulls, no bulk exports, no access to charts you haven't opened. The extension only works on the page in front of you.
Each practice is walled off.
Practice data is isolated at the database level with row-level security. One practice can't see, query, or be shown another's data.
You attest. AuthAI assists.
Nothing changes in your note unless you accept it, and nothing is ever submitted to a payer on your behalf. The clinical judgment stays yours.
Every flag shows its source.
Suggestions cite the payer policy or coverage document they come from, so you can verify them instead of trusting a black box.
For your compliance lead
Questions we'll answer before go-live.
- Which data elements leave the browser?We'll show you the exact fields, from your own EHR, before you turn it on.
- What is stored, and for how long?We'll walk through retention for your practice and what's deleted when.
- Which vendors process data?A full list of subprocessors and what each one touches.
- What agreements are in place?We'll review business associate terms with you directly during onboarding.
Get it right
the first time.
Join early access and we'll set AuthAI up for your practice ourselves.