How Eva compares

How Eva compares to a typical AI dental scribe

This is a category comparison, not a call-out. We compare Eva to the shape of a typical AI dental scribe, and every Eva capability is tagged with where it stands (shipped, in testing, or on the roadmap) so you can check each one.

The whole loop

Most scribes stop at the note. Eva starts there.

The note is what you can test today. Here is where the rest of the loop stands.

Shipped

The clinical note

Record or upload a consult, get a source-grounded note you review and copy to your PMS, plus a Team Brief and Patient Assessment. This is the demoable-today core.

In testing

Case, plan & pipeline

Treatment plans and fees, the case pipeline and attention queues, and in-treatment-to-completed tracking are built and running. They are being validated, not yet a day-one promise.

On the roadmap

Follow-ups & outbound

Template Studio, generated follow-ups, and automated outbound (SMS, WhatsApp, email) are on the roadmap. They'll appear here, tagged shipped, when they land.

Five dimensions that matter

Where Eva is different, and what she's still building

Each row states the general pattern for a typical scribe, then Eva's real answer, tagged with the maturity of the Eva capability it describes.

Scope

A typical AI dental scribe

Most AI scribes stop at the note: a transcript in, a structured note out, and the workflow ends there.

Eva

Shipped

Eva starts at the note and is built to carry the case to completion. The source-grounded note is what you can use today; case building, treatment plans, and the pipeline are built and in testing; follow-ups, outbound, and reporting are on the roadmap.

Your audio

A typical AI dental scribe

Many scribes give the clinic no control over recordings, or a single fixed retention window you can't change.

Eva

Shipped

You choose what happens to raw audio: keep it (the default), delete it once a note is signed, or delete it after a set number of days. Only the raw audio is ever deleted; transcripts and clinical notes are always kept as your record, and every deletion is written to a tamper-evident audit trail.

The paperwork

A typical AI dental scribe

The clinic is often left to source its own consent wording and data agreements, or handed a marketing badge instead of a document.

Eva

Shipped

Eva provides a consent pack and a data-processing agreement (DPA) on request, so your practice can put the paperwork in place with its own counsel. These are drafts you review. Eva supports the workflow; she does not replace your legal review.

Claims & evidence

A typical AI dental scribe

It's common to see broad “HIPAA compliant” or “certified” claims, or a host's certifications presented as the product's own.

Eva

Shipped

Every security control is tracked at its true status on Eva's security page, and the named subprocessor register is available for your reviewer to check: no borrowed badges, no blanket claims.

Control

A typical AI dental scribe

AI documentation tools vary in how much they leave to the clinician; some auto-populate the record directly.

Eva

Shipped

Eva never diagnoses, never prescribes, and never writes into your practice-management system on her own. A clinician reviews and finalizes every note, and your team copies the finalized note into the record.

Where a row describes work that isn't finished, it carries an In testing or On the roadmap tag.

Compare Eva on a real consult, not a spec sheet

Book a walkthrough and we'll run the capture → draft → review flow end to end — and answer, on the record, exactly where each part of the loop is.