auro
auro EHR

Ask once.Approve once.

auro is the record with a staff inside it. Say what needs doing; the desks do it in parallel, on the chart, the payer and the ledger, and nothing leaves the practice until you approve.

Lana’s computer· laptop
portal.example-payer.test
Drug requested
Tirzepatide 15 mg (Zepbound) · fictional request
Clinical criteria
BMI of 30 or more, or 27 with a weight-related condition
Cardiometabolic risk documented (a recent A1c)
One prior weight-loss agent tried and stopped
Lifestyle program for 3 months or more
Diagnosis (ICD-10)
Current BMI
Opening the request
Opening the portal · 0 of 9
Lana’s computer· ePA
ePA · NCPDP SCRIPT (fictional) · opening
Opening the ePA connection

Fictional practice, patients, plans and portal. Prior auth submission, by portal and by ePA, is in construction and runs here against test endpoints.

Behind: NLM Historical Audiovisuals · MEDLINE terminal film, 1970s · NARA RG 111 · Army Signal Corps

Recorded from the live product

Twenty-five seconds. One morning, start to finish.

The morning brief, a question asked out loud, the evidence read, Lana on the phone with the payer, and the prior auth ready for one approval. Screen captured from the app on a fictional practice.

Your team, at your @

Mention a desk. It answers in the thread.

Nine desks live in Team: Front desk, Intake, Billing, the Care coordinator, Lana, Bookkeeper, Purchasing, Payroll and the Practice manager. @ one, and the work shows up as one step with its mark. Desks hand off to each other in the open, and anything that leaves the practice stops for you.

# general The whole practice · fictional

An animated recreation, drawn from Team v2’s own components and copy. The film above is the real thing.

Agent computer

Lana gets her own computer. You can watch every click.

Payer portals and vendor sites rarely have an API. So Lana works them the way a person would: a real browser on a machine auro runs, docked beside the run so you can watch, replay, take over or stop. Prior auth submission in construction

LLana’s computerPrior auth · Wegovy · Priya Natarajan (fictional)
Working · 0:04
portal.example-payer.test / prior-authorization
Payer portal (fictional)
Home
Drug policies
New request
Request status
Messages
New drug prior authorization
Semaglutide 2.4 mg (Wegovy) · weekly injection · fictional request
Prescriber NPI
Member ID
Diagnosis (ICD-10)
Current BMI
Prior agents tried
Submit request
auro · chart
PN
Priya Natarajan (fictional)44 · commercial plan (fictional)
COVERAGE
Eligibility (271)Active · pharmacy benefitactive
Prior auth requiredPolicy Pulseyes · cited
EVIDENCE
A1cLab, Sep 128.4%
BMI history4 readings, 10 months36.9
Prior agentsPhentermine, 3 mo, stoppedconfirmed
Lifestyle programDietitian visits since Mar7 mo
a
Reading the 271
Lana’s computer · Wegovy for Priya Natarajan (fictional) · commercial plan (fictional)
Prior auth 0/9

A replay drawn in the page. The portal is a fictional test site, the NPI is a test number and the patient is invented. Press Approve to see the rest of the run.

Watchable, stoppable, and it waits at the door.

  • Hardware auro controlsThe computer runs on a machine auro operates, not a third-party cloud browser, because the screen holds patient data.
  • Every risky click waits for youSubmit, pay, send and sign stop at “Review with you”. The portal’s Submit stays held until you approve.
  • Take over at any momentTake over pauses Lana and hands you the mouse. Stop ends the run and tells you exactly what was and wasn’t sent.
  • Replay any stepOne segment per step on the scrubber. Click a row in the checklist to see that moment again.
  • About 21 seconds to fill a test portalMeasured on our fictional test portal, from opening the request to waiting for you.
Prior auth, end to end

Lana does the work. You open the one door.

Lana fills the payer’s portal on her own computer, or answers the plan’s ePA questions straight from the chart, with the source beside every answer. Then everything waits for one approval, with Face ID. Prior auth submission is in construction and runs here against test endpoints.

Lana’s computer· laptop
portal.example-payer.test
Drug requested
Tirzepatide 15 mg (Zepbound) · fictional request
Clinical criteria
BMI of 30 or more, or 27 with a related condition
Cardiometabolic risk documented
One prior agent tried and stopped
Lifestyle program for 3 months
Diagnosis (ICD-10)
Current BMI
Opening the request
Opening the portal · 0 of 9
Lana’s computer· ePA
ePA · NCPDP SCRIPT (fictional) · opening
Opening the ePA connection
Needs you · external · 2 prior auths
Send Paul’s portal request and Priya’s ePA answers
Every answer traced to the chart · re-checked at send
Approved by Dana Lin with Face ID
Ask the evidence

A clinical question, answered with its sources.

Ask in Today the way you’d ask a colleague. The evidence model searches the published literature from your device, keeps only the facts that check out against their source, and shows how sure it is. It is decision support: you decide.

auro evidence answers: a question about protein and lean mass on GLP-1 therapy, with journal cards landing on a rail, each with its study type and one fact.
Recorded from auro’s evidence answers. Real published papers; each card shows its study type and one fact.Evidence answers are in testing.
Decision support · you decide
Source viewer · 1 of 4abstract
Body composition changes during weight reduction with tirzepatide in the SURMOUNT-1 study
Look M et al. · Diabetes Obes Metab · 2025 · RCT substudy · n = 160
About 25% of weight lost on tirzepatide was lean mass, the same share as placebo.
Lines stand in for the abstract. In the product the abstract itself opens here, with the sentence each fact came from highlighted.
Chapter two · your auro team

Nine desks. One practice manager watching the clock.

Each desk owns its outcomes and sees only its lane. The practice manager hands out the work and says what is stuck and why.

The audit trail

Every action, sealed. The agents included.

Each read, draft and approval becomes one entry that carries the hash of the one before it: who did it, for whom, why, and who said yes. Ids only, never note text. No role can edit an entry, and copies of the chain head are checked from outside the database.

Audit trail· today · fictionalAppending…
Chain verified · 0 entries · 0 gaps · head copied off the database
What you can ask

Twelve runs. Each one stops at your door.

0model calls on the server that runs Today’s tools. Planning happens on your device.
1approval at the door for anything that leaves the practice, with Face ID or a passkey.
9desks, each with its own permissions. Purchasing sees no patient data.
11clinical tables that keep every change, beside an append-only, hash-chained ledger.

What we don’t claim

  • There is no government “HIPAA certification”, so we don’t say we have one. We build to the HIPAA Privacy and Security Rules and will walk you through each control.
  • Practices sign a business associate agreement with auro in the app. Among the services that process data for us, Deepgram’s BAA is signed; the others are in progress.
  • Evidence answers are decision support, and are in testing. The clinician decides.
  • Prior auth submission (portal and ePA), the agent computer and Payroll are in construction. Some older features still call hosted models; each is listed in our model register.
  • The films are recorded from the running app on a fictional practice. Payer and vendor names are swapped for placeholders.

See it run on your practice’s day.

We’ll set up a fictional copy of your schedule and payers and run a morning with you, approvals and all.