An Open Dental follow-up integration can use PMS data to identify treatment opportunities, check appointment status, avoid contacting patients whose state has changed, and write communication context back into the practice workflow. The exact implementation depends on the approved API scope and the practice's configuration.
What Open Dental data matters for follow-up?
For an unscheduled-treatment workflow, the important objects are not every field in the PMS. The core questions are whether a treatment plan or treatment-planned procedure exists, whether the relevant appointment is already scheduled, whether the patient is on an unscheduled list or has a planned appointment, and what communication history already exists.
Open Dental's public API documents treatment-plan retrieval, appointment retrieval and creation, planned appointments, appointment status values including UnschedList, and communication logs. A production integration should still be tested against the office's version, configuration, and approved API permissions.
How an unscheduled treatment workflow can work
- Treatment plan
- Validate status
- Eligible queue
- Follow-up
- Reply
- Schedule / route
- Close
A practical flow can start by finding active treatment context, then checking appointment state before any outreach. If the patient remains eligible, the system can place the opportunity into a recovery queue. A reply can then be routed by scheduling need, timing, cost concern, or a question that requires human review.
If the patient becomes scheduled, the workflow should stop or update rather than continuing an outdated sequence.
Why status checks matter
A follow-up list becomes stale quickly if the system does not re-check the PMS. Before sending a message, verify that the treatment opportunity is still open and the patient has not already scheduled, completed, declined, or moved into another current state.
This is the difference between simply importing a list once and maintaining a synchronized workflow.
Write-back and communication history
Front-desk teams should not have to reconstruct the same conversation in multiple systems. Open Dental exposes communication-log data through its API, which can support a design where relevant follow-up activity or notes are kept visible in the practice record, subject to implementation rules and permissions.
The useful outcome is not “another inbox.” It is a workflow where staff can see what happened, what the current status is, and what the next action should be.
What a vendor should show in a demo
- How treatment opportunities are identified from Open Dental.
- How the system verifies that the patient is still unscheduled.
- What happens when the patient schedules after entering the queue.
- How replies are routed and owned.
- What information is written back or synchronized.
- How opt-outs and suppression rules are enforced.
- How the workflow handles clinical or sensitive replies.
Also ask whether the vendor uses Open Dental's supported API path and what setup is required at the office.
Frequently asked questions
Can Open Dental expose unscheduled appointments through its API?
Open Dental's appointment API documents appointment status values including UnschedList and supports retrieving appointments by status.
Can software create or schedule appointments in Open Dental?
The public API documents appointment creation, planned appointments, scheduling planned appointments, and slot lookup. A vendor should explain exactly which functions its integration uses and what office configuration is required.
Can communication notes be read from Open Dental?
Open Dental documents communication-log retrieval through its API. Whether a specific vendor writes information back, and in what format, depends on that vendor's implementation and permissions.
Should follow-up stop when a patient schedules?
Yes, a well-designed recovery workflow should re-check current state and stop or update outreach when the relevant appointment has been scheduled.
For the broader workflow, see unscheduled treatment follow-up and follow-up by patient intent.