Straight answers

Eva is the treatment completion engine for dentistry: she turns a spoken consult into a source-grounded clinical note, a patient-readiness assessment, and a tracked case — carrying treatment from diagnosis toward done, with the clinician in control. What you can test today is the note, the Team Brief, the Patient Assessment and Consult Intelligence; the case layer beyond them is built and in testing.

Eva drafts every note from your captured consult (the transcript and your team's notes). She keeps ambiguous findings general rather than guessing. What she adds is your own template's expected normal for a routine check nobody mentioned, always marked “please verify” so an assumption is visible rather than silent; that coverage is partial today, so some fields still come back blank. She reports fees from what was said rather than inventing them, and never silently changes an amount. Every note is a draft: Eva cannot write it to your chart, a person copies it in, and the clinician sign-off is recorded when given.

Yes. This is built and in testing (the note, Team Brief, Patient Assessment and Consult Intelligence are what you can test today). Eva turns a consult into a proposed treatment plan and case you can shape, an editable layer seeded from the note. The note itself stays your untouched clinical truth; editing the case never changes the note.

A front-desk-ready view of the verified consult, so your coordinator picks up exactly where the clinician left off without re-reading the whole note. It's built from the note you already signed — Eva restates that note for the front desk rather than going back to the recording.

Eva is designed for HIPAA-aligned deployment and built toward GDPR / UK GDPR alignment, with encryption, per-clinic isolation, and a tamper-evident audit trail in place today. The signed agreements and formal assessments behind claims like “HIPAA compliant,” “certified,” or “BAA signed” are still in progress; the security page tracks each one at its current status.

Patient data is only ever sent to reviewed, approved providers — anything off the approved list is refused at the point of sending. Data is encrypted in transit (TLS) and at rest (AES-256). Our specific infrastructure and named subprocessors are proprietary but available to you and your compliance reviewer on request, under NDA.

The practice owner can require an authenticator-app code to open the clinic account, on top of the password. Because only the owner's authenticator generates that code, a stolen email and password alone can't open the account remotely — the sign-in stops at the code screen. It's opt-in per clinic and already enforced on Eva's own account; if the authenticator is lost, the Eva team resets it.

Patient data is never used to train our AI providers' models; we select providers that offer no-training / zero-retention terms. Eva's own learning is opt-in and de-identified — it's off by default, and only ever uses de-identified examples reviewed by our team, never sent to a vendor for training.

You control it. Keep raw recordings indefinitely (the default), delete them once a note is signed off, or delete them after a set number of days. Only the raw audio is deleted this way — transcripts and clinical notes are kept as your record.