Official API Integration
Designed to keep your Open Dental chart in sync — from intake to follow-up.
mConsent integrates with Open Dental via the Open Dental API and is designed to write digital intake forms, reminders, payments, and AI-assisted call data back to Open Dental and other major PMS — so your front desk avoids manual re-entry and your chart stays current.
Designed to remove the manual re-entry between front desk and chart.
Most Open Dental practices already collect intake data, send reminders, and take payments — but in pieces. mConsent is designed to connect those pieces and write the result back into Open Dental.
Digital intake to chart
Designed to push completed intake responses, signatures, and demographics back to the patient’s Open Dental chart so the front desk avoids manual re-keying.
Reminder & confirmation status
Designed to log SMS and email reminder activity against the appointment in Open Dental. SMS uses TCPA-compliant consent language and STOP-to-unsubscribe handling.
Payments & financing
Designed to record patient payments and financing activity from mPayr against the patient’s ledger, keeping Open Dental posting consistent with what was actually collected.
AI call summaries
Designed to attach Zaha AI call transcripts and summaries to the patient record. AI is designed to route and summarize — not to make clinical determinations.
Insurance details (one-way)
Insurance details captured on intake are designed to populate Open Dental fields — one-way, mConsent into Open Dental. Bi-directional insurance sync is under development. Available fields depend on your Open Dental configuration and may change as Open Dental updates its API.
Configurable sync cadence
Designed to let your practice configure how frequently the connector syncs with Open Dental — from on-event to scheduled batches — based on what your team needs.
One workflow, with Open Dental as the source of truth.
Open Dental continues to be the system of record. mConsent is designed as a workflow layer that captures patient responses, payments, reminders, and call activity — then writes the result back to the chart with the cadence your practice configures.
The modules that read or write to Open Dental.
Available data fields, sync cadence, and supported workflows depend on your Open Dental version, your network configuration, and options selected during onboarding.
Paperless Intake
Designed to collect intake forms, signatures, insurance details, and medical history before the visit and post results to the Open Dental chart.
Communication
Designed to send reminders, confirmations, and 2-way patient messaging with TCPA-compliant consent and to log activity against the Open Dental appointment.
mPayr
Designed to take patient payments at the chair, by text-to-pay, or after the visit and to record the transaction against the Open Dental ledger.
Zaha AI
AI phone coverage designed to route routine scheduling calls and attach call summaries to the patient record.
Insurance Concierge
Designed to run eligibility and benefits workflows around the appointment and surface the result alongside the patient record.
Online Scheduling
Designed to write requested appointments back to Open Dental with the operatory, provider, and appointment-type rules your practice configures.
mConsent is designed to work with Open Dental and other major PMS.
If your practice runs Dentrix, Eaglesoft, or a different system, the same connector pattern applies. Specifics are confirmed during onboarding.
Common questions about the Open Dental connector
Quick answers about how mConsent is designed to work alongside Open Dental.
See how mConsent fits your Open Dental setup.
A short demo designed for your stack — intake to chart, payments to ledger, reminders to appointment. Subject to your master services agreement.
Capability described on this page is illustrative based on typical configurations; actual results vary by Open Dental version, network, and practice. Pricing and program terms are governed by the MSA at activation. mConsent operates as a Business Associate under HIPAA and executes a BAA with client practices.
Full Disclosures & Trademarks
Integration scope
mConsent integrates with Open Dental using the Open Dental API. mConsent is an independent software vendor and is not affiliated with, endorsed by, or sponsored by Open Dental Software, Inc. Open Dental remains the practice’s system of record; mConsent operates as a workflow layer that reads from and writes back to Open Dental subject to the API permissions enabled at your practice.
Connector capability
mConsent is designed to read and write supported data with currently-supported Open Dental versions. Available data fields, posting behavior, sync cadence, and supported workflows depend on the Open Dental version installed at your practice, the Open Dental API module being enabled, your network configuration, and options selected during onboarding. mConsent does not promise feature parity across every Open Dental version or environment, nor across every other PMS referenced on this page.
SMS, voice & TCPA
Where any feature on this page sends a message to a patient — reminders, confirmations, payment links, or AI-assisted call workflows — the system is designed to capture express patient consent and to honor opt-out requests consistent with the federal Telephone Consumer Protection Act (TCPA), state messaging laws, and carrier requirements. The practice is responsible for the lawful use of these features — including how it obtains, records, and refreshes consent.
Pricing & MSA
All commercial terms — including pricing, included modules, available integrations, support hours, and uptime objectives — are governed by the master services agreement (MSA), order form, and applicable schedules executed between mConsent and the practice. Marketing copy on this page is descriptive of intended capability and does not modify or supersede those agreements. In any conflict, the executed agreements control.
Trademark attribution
Open Dental is a registered trademark of Open Dental Software, Inc. Dentrix is a trademark of Henry Schein One, LLC. Eaglesoft is a registered trademark of Patterson Dental Supply, Inc. mConsent is an independent software vendor and integration provider. Reference to these systems on this page is for identification purposes only.
HIPAA & protected health information
mConsent operates as a Business Associate under HIPAA and executes a Business Associate Agreement (BAA) with each customer. Patient information processed through Open Dental-connected workflows — intake, reminders, payments, and call summaries — is handled under the terms of the BAA, the practice’s Notice of Privacy Practices, and applicable federal and state laws. The practice remains responsible for its own use of the platform, including the consents it relies on.
Verified figures & forward-looking language
Aggregate platform figures referenced on this page are limited to: 5,000+ practices served since 2017, 5.5M+ patients, 30M+ documents processed, and 11M+ appointments handled across the platform. They reflect lifetime cumulative totals from mConsent system logs since 2017 and are not annualized. They are not a forecast or guarantee of any individual practice’s results. Phrases such as “designed to,” “intended to,” “built to,” and similar describe how a feature is engineered to behave in typical configurations and are not promises of any specific outcome, response time, or revenue impact for any individual practice. Outcomes vary based on practice size, configuration, staffing, and external factors outside mConsent’s control.
Testimonials & case studies
Any testimonials or case studies referenced on this page or elsewhere on the mConsent site represent individual practice outcomes and are not typical results. Your results may differ. mConsent makes no representation that any particular practice will achieve similar outcomes.
