Scheduling and charting that stand on their own
Columns, operatories, perio, odontogram, treatment plans and the ledger. Feature parity with the incumbent, because you cannot sell a front-desk layer to a practice that still needs the old one open.
Voted #1 HIPAA-compliant AI for healthcare
HIPAA-compliant AI that does the front desk’s worst work.
Type what needs doing. Enamel verifies tomorrow’s insurance, fills the hole a cancellation left, works today’s denials and briefs the huddle — inside a dental practice management system that stands on its own.
The demo is synthetic data, resets nightly, and has every outbound channel switched off. Nothing in it can text a patient or file a claim.
Four things it does, on a loop. Pick one, or let it run.
The operator verifies every insured patient on tomorrow's schedule against the carrier portals and flags the two that will not pay as booked.
Tomorrow · Thursday 12 March
9 insuredHarold Nunez
Active · $1,140 leftDana Cole
Downgrade · $310 patientPriya Raman
Active · $1,500 leftMarcus Webb
Terminated 1 MarSofia Lindqvist
Active · frequency metTerrell Boyd
Active · $860 leftDana Cole · MetLife PDPAlternate benefit
- Planned
- D2740 crown, porcelain/ceramic
- Plan pays
- D2751 · 50% · $412.00
- Patient portion
- $310.00
- Confidence
- 0.97 · read from portal
Benefit breakdown captured from the carrier portal, with the screenshot it was read from attached to the patient's record.
No migration required
Runs over the practice management system you already own
enamel-sync performs real two-way synchronisation, so Enamel can be the front-desk layer on Monday and the system of record whenever you decide — or never. Nothing is exported, re-keyed, or held hostage either way.
- Dentrix
- Open Dental
- Eaglesoft
- Curve
- Denticon
- CareStack
And it replaces the bolt-ons: Weave, NexHealth, Modento, Vyne and DentalXChange — one system, one patient list, one invoice.
The platform
Everything the practice runs on, in one system
The assistant is the reason people call; this is the reason they stay. Enamel is a complete practice management system, and the AI is a colleague inside it rather than a chat window bolted to the side of somebody else’s database.
Claims, ERAs and an A/R you can trust
Every balance carries a settlement state and a reason, so “is this number real?” is something you read rather than something you investigate.
Eligibility from carriers that have no API
A browser that carriers accept, driven by an agent that returns a structured benefit breakdown with a confidence score and the screenshot it read it from.
Two-way SMS and email, on our own trunks
Reminders, recall, forms and payment links come from the same system as the schedule — not a second vendor with a second invoice and a third copy of your patient list.
Imaging, including the big studies
DICOM in, a viewer that opens, and CBCT that does not have to be handed off to a workstation in the back.
An open API with no integration tax
REST, FHIR R4, webhooks, a published OpenAPI document and a public sandbox. No partner program, no certification fee, no bridge polling a database in the sterilization closet.
The numbers the owner actually asks for
Production, collections, unscheduled treatment, hygiene reappointment and provider mix — computed once, reconciled nightly, and the same in every report.
Real two-way sync, so adoption needs no migration
enamel-sync talks to Dentrix, Open Dental, Eaglesoft, Curve and the cloud PMSes. Keep your system of record on day one and change your mind later.
Security and HIPAA
The assistant never sees a patient
Not “is instructed not to”. Cannot: protected health information is replaced with an opaque handle before the request leaves our infrastructure, and resolved back to a value in the browser that is already entitled to it.
The model never sees your patients
PHI is replaced with an opaque handle before anything reaches a model, and resolved back to a value in the browser that is allowed to see it. The assistant reasons over “patient #a41f”, not over a person — and that is a property of the channel, not a prompt asking it nicely.
A BAA, signed, before a single record moves
HIPAA Security Rule controls are implemented and mapped, encryption is on at rest and in transit, and every access to a record is written to an audit log that the practice can read without asking us.
One practice cannot read another
Tenant isolation is enforced in the database with row-level security, and a test in the pipeline tries to cross the boundary on every commit. A control that exists only in a security document is worse than no control.
The agent cannot speak as you
It verifies insurance, reads EOBs and triages denials. It will not answer your phone or text a patient in your name — enforced by the agent having no tool that can reach one, not by policy.
{
"task": "verify_eligibility",
"patient": "phi:a41f9c2e",
"carrier": "MetLife PDP",
"planned": ["D2740", "D0274"],
"asks": ["coverage", "frequency",
"downgrade", "remaining_max"]
}No name, no date of birth, no member ID, no note text. phi:a41f9c2e is a handle the practice’s own service resolves — and a test in the pipeline captures the exact bytes sent to the model and fails the build if a patient value appears among them.
Voted #1 HIPAA-compliant AI for healthcare
Why practices pick it
It does the work, not the summarising
The operator signs in to carrier portals, posts remittances, drafts appeals and offers open slots. The output is a booked appointment or a filed appeal, not a paragraph about one.
It stops at the line you would stop at
Anything that speaks to a patient or spends money waits for a person. That is a property of which tools the agent has, not a sentence in a prompt, and the boundary is written down in our engineering docs rather than implied in a brochure.
It is one system, not six subscriptions
Scheduling, charting, claims, imaging, messaging and analytics under one login, one patient list and one audit log — which is also the only way the assistant can answer a question that crosses two of them.
Questions
The things practices ask first
Is Enamel HIPAA compliant, and will you sign a BAA?
Yes to both. Enamel Cloud LLC signs a Business Associate Agreement before any patient data is loaded. Data is encrypted in transit and at rest, access is least-privilege and logged, tenant isolation is enforced in the database rather than in application code, and the AI assistant is architecturally prevented from receiving protected health information.
Does the AI read our patients' records?
No. Sensitive values are swapped for opaque handles before any request leaves our infrastructure, so the model works with references and the real values are rendered in your browser. Nothing you would call PHI appears in a model's context window, and a test in our pipeline captures the exact bytes sent to the model and fails the build if a patient value appears among them.
Do we have to migrate off Dentrix or Open Dental first?
No. enamel-sync performs real two-way synchronisation with Dentrix, Open Dental, Eaglesoft, Curve, Denticon and the cloud systems, so you can run Enamel as the front-desk layer over the practice management system you already own and move the system of record later, or never.
What does Enamel replace?
The front-desk stack first: patient communication, reminders, recall, forms, online booking, eligibility verification and the claim follow-up spreadsheet. If you want it to, it also replaces the practice management system itself — scheduling, charting, perio, treatment planning, claims, ledger, imaging and analytics are all in the product.
How does insurance verification work without a carrier API?
Most carriers have no API worth the name, so Enamel signs in to the portal the way a person does, with a browser carriers accept, and an agent extracts a structured breakdown — coverage, frequencies, downgrades, remaining maximum, history. Every result carries a confidence score and the screenshot it was read from, so an unsure answer is visibly unsure rather than quietly wrong.
Can we build on it?
Yes. REST and FHIR R4, outbound webhooks, a published OpenAPI document, a public sandbox and free SDKs. There is no partner program and no integration fee — the integration surface is the product, not an upsell.
How do we try it?
The demo at demo-app.enamel.cloud runs on synthetic data, resets nightly and has every outbound channel disabled, so you can click anything in it. Nothing in the demo can text a patient or file a claim.
See it do tomorrow’s insurance
The demo is a whole practice — schedule, charts, claims, the assistant — on synthetic data that resets every night. No form, no call, no credit card.
Questions a demo will not answer: [email protected]