Authorized visit input
Conversation, typed data, or six-site measurements begin in Molaris.
Molaris × Open Dental
From conversation to deliberate writeback.
Molaris prepares clinical work from the authorized visit, keeps it reviewable, and waits for the relevant clinician action before sending anything to Open Dental.
“Integrated” is not enough. The destination, fallback, and unsuccessful state should all be visible.
The workflow makes preparation, decision, and destination separate.
Record → review → approve → write.
Reviewable artifact
The note, working exam, or referral remains inspectable.
User action
Approval, exam finalization, or Send initiates the consequential step.
Open Dental API
The response determines preferred, fallback, or failed status.
Every artifact has a specific destination and an honest unsuccessful state.
Know what crosses the boundary.
After explicit approval, Molaris first targets the associated appointment. When no matching appointment is available, a commlog is used and identified as the fallback. The approved note is locked; a correction becomes a separately approved amendment.
When supported by the practice’s Open Dental API, the finalized six-site exam targets the Perio module. If the intended endpoint is unavailable, Molaris can use a named commlog summary fallback rather than claiming the Perio write succeeded.
Saving a draft does not file it to Open Dental. The user’s Send action delivers the email/PDF, and only a successfully sent referral can file a copy to the patient chart.
A failed API request is reported. It does not erase the Molaris record or silently change into a successful Open Dental status.
Open Dental already offers native voice periodontal entry. The products should be compared on the jobs they actually perform.
Command entry and ambient drafting are different tools.
Open Dental’s built-in tool listens for supported commands while the user charts periodontal measurements. If direct native voice entry is the entire need, evaluate that first. Read Open Dental’s documentation →
Molaris combines ambient note drafting, a six-site working exam, referral preparation, explicit approval, signed-note locking, amendments, and visible writeback outcomes.
An integration earns trust in the paths where the upstream system rejects or cannot accept a request.
A failed write is not a vanished record.
The user keeps a usable, inspectable state.
- The Open Dental error remains visible.
- The signed content stays available in Molaris.
- A fallback is labeled as a fallback.
- Referral links require a human confirmation instead of mutating on email-link open.
- Retry and duplicate-prevention paths should be verified in the practice’s real environment.
Compatibility depends on the practice’s API access, permissions, version, identifiers, and configured endpoints.
Verify the real environment.
- API access
- Open Dental API access must be enabled, reachable, and permitted for the intended operation.
- Credentials
- The practice customer key is stored server-side. Unsaved keys may be used only for the connection test; other calls use the practice-scoped stored key.
- Patient and appointment mapping
- Writeback depends on the correct PatNum and, for an appointment note, the intended AptNum or a matching same-day appointment.
- Perio support
- Verify the required periodontal endpoints and accepted fields against the practice’s Open Dental version.
- Pre-production test
- Use a test practice to verify success, fallback, failure, retry, duplicate prevention, and permission errors before clinical deployment.
Open Dental is a third-party product. This page describes the current Molaris integration behavior and does not imply endorsement by or affiliation with Open Dental Software.
Don’t take “integrated” on faith.
Use fictional data to inspect the draft, approval gate, locked record, amendment, destination, fallback, and failure states yourself.
Try the live workflow →