Setup required
Insurance claims
Prepare claim files and eligibility checks through an adapter shaped for DentalXChange, Vyne, Availity and Change Healthcare. A live payer connection requires a signed clearinghouse agreement.
What connects
Integrations built around a working clinic
Each connection is listed with its current status, so you can plan around reality instead of a sales promise.
Documents ready
Imaging & documents
Attach X-rays, intraoral photos, lab reports, consents and scanned documents directly to the patient chart. DICOM viewer integration and external imaging vendor bridges are available; a direct X-ray sensor bridge is not included today.
Included
Payments
Take monthly or annual subscriptions through PayPal, and record cash, card, transfer and insurance payments in the patient ledger and practice reports.
Included
Data migration
We migrate patient records, appointments, treatment history and core billing data during onboarding, with a full backup of your source system kept on your side.
Configurable
Communication
Automated appointment reminders use Twilio for SMS/WhatsApp and SMTP for email, configured for your deployment. Two-way replies and Y/N confirmations are supported.
Included
Reporting
Practice dashboards, production, receivables and audit reports use the same data, with printable documents for patients, payers and internal review.
API available
API & webhooks
Scoped read/write API keys cover patients, appointments, payments and invoices, with per-key site scope and usage controls. OpenAPI 3 documentation, signed partner webhooks and a developer portal support custom workflows.
Included
Patient portal
Patients can view appointments, update their details, complete intake and pay online. Online self-scheduling is built into the same workflow.
How it works
From first call to a working connection
Scope the connection
We map the service, the data flow and who owns the credentials before anything is configured.
Put the agreement in place
Clearinghouses, imaging vendors and payment providers have their own agreements. We tell you which one is needed.
Configure and test
We connect the service, run a test file or workflow and confirm the result before your team relies on it.
Current boundaries, stated plainly
- The clearinghouse adapter is a sandbox today; live payer connections require a signed agreement.
- There is no digital X-ray sensor bridge. DICOM viewer integration and external imaging vendor bridges are available.
- SmileCare does not run side by side with Dentrix or Eaglesoft; data is migrated during onboarding.
- Public APIs and signed webhooks are available; a self-service partner marketplace is not yet offered. Custom integrations are available on the Multiple clinics plan.
FAQ
Integration questions
Does SmileCare replace my imaging system?
Not today. SmileCare stores images and documents such as X-rays, intraoral photos, lab reports and consents in the patient record. DICOM-capable imaging can be scoped during deployment, but there is no digital X-ray sensor bridge in the product today.
Can SmileCare send claims directly to insurance?
Claims go through a clearinghouse adapter. The adapter is shaped for DentalXChange, Vyne, Availity and Change Healthcare, but a live payer connection requires a signed clearinghouse agreement. Until that is in place, the adapter is a sandbox for preparing and testing claim files.
Do you integrate with Dentrix or Eaglesoft?
We do not run alongside those systems. Instead, we migrate patient records, appointments, treatment history and core billing data into SmileCare during onboarding. You keep a backup of the old system for your records.
Is there an API for custom integrations?
SmileCare exposes scoped read/write APIs for patients, appointments, payments and invoices, with per-key site scope, usage controls, OpenAPI 3 documentation and signed webhooks. A partner marketplace and bespoke integrations are Group-plan conversations.
Ready to see how SmileCare fits your practice?
Start your 30-day free trial, or walk through your workflows with our team. No credit card required.