Skip to content

Patient data is handled like patient data.

Encryption, practice isolation and human approval are built into SmileOps. This page says what each one does.

People approve what goes out.

Replies, appeals, payment postings and campaigns wait in the Inbox for a named reviewer. Every agent run is recorded in the audit trail.

How patient data is protected.

A BAA firstA business associate agreement is signed before any patient data.
Encrypted identifiersNames, phones and dates of birth are encrypted with AES-256-GCM.
Each practice isolatedRow-level security keeps one practice’s records out of another’s.
Two-step sign-inEvery staff account uses multi-factor authentication.
People approveAnything sent to a patient or payer waits for a named reviewer.
Audit trailEvery agent action is recorded with who approved it.

The data belongs to a patient.

Names, phone numbers and dates of birth are encrypted, and each practice’s records are kept apart from every other’s.

A dentist shows a patient a model of teeth while explaining treatment.

Patient identifiers encrypted· AES-256-GCM

Assistance you can inspect.

01

Practice access

The workspace applies organization, location and role context to protected records. Access should match the responsibilities of the person using it.

02

Review boundaries

Drafts, recommendations and consequential actions have distinct review requirements. Approval does not bypass integration capabilities.

03

Visible outcomes

A completed action needs an observed result. Failed, blocked and unconfirmed work must remain distinguishable from success.

What is settled before patient data is connected.

Review the actual data flow and services involved in your chosen workflow. Confirm access, agreements, provider configuration and operational responsibilities before using patient information.

01

Data and providers

Identify the records the workflow needs and the services that process them. Required agreements and provider safeguards are reviewed with you before go-live.

02

Permissions and review

Agree on authorized users, review owners and escalation paths. Configure the workflow around those responsibilities.

03

Connection scope

PMS, phone, messaging and financial connections are each authorized separately.

FAQs

Want to talk through your setup?

Book a demo
What security information can we review?

Review our security documentation, data flows and required agreements with our team. Our compliance program includes an independent HIPAA assessment before the first founding practice goes live, with SOC 2 Type I planned for 2027 and Type II for 2028.

Can an approval change a patient record by itself?

No. Your approval, the connection’s permissions and a confirmed result are separate steps. SmileOps keeps each step visible so your team knows what has been proposed, approved and completed.

Can we evaluate without patient information?

Yes. We take data privacy seriously. Our walkthroughs use example data so you can explore SmileOps without sharing patient or practice information.

See SmileOps on a call with your team.

We walk through your phones, insurance and reports on the PMS you use.

An empty dental treatment room with a teal chair, a bright window and white cabinets.