You keep Open Dental. It stays your schedule, your chart and your source of truth. We read from it and write back into it through the API Open Dental publishes for third-party software, using a key you can switch off from inside Open Dental whenever you want.
From your Intake.Dental dashboard you click Get my key. We create an Open Dental customer key for your office through Open Dental's developer program and show it to you with paste instructions. You don't have to request one from Open Dental or figure out permission tiers. Open Dental charges the developer, which is us, for API access per location, so it is not a new line on your Open Dental bill.
On the server, open Open Dental and go to eServices > eConnector Service. 'Current eConnector Service Status' should say Working. Then in Open Dental go to Setup > Advanced Setup > API, check Enabled, click Add Key and paste the key we gave you. That's the whole change on your side. Steps one through three take about five minutes.
Click Connect in the dashboard. We save the key, make a test read against your Open Dental to prove the eConnector answers, and mark the office connected. The first sync looks back about two years of appointments and procedures, plus your patient list, and the dashboard shows the last time your eConnector responded so you can see the connection is alive.
Writes into your chart happen in real time, the moment the feature that needs them runs: a confirmed text, a paid text-to-pay link, a filed fax, an approved note or a booked call. To keep our side current we read changed appointments and procedures from Open Dental every 15 minutes and walk the patient list, and heavier pulls (insurance details, claim history, recalls, image metadata and files, adjustments) run on a nightly and periodic schedule.
What we don't write, so nobody is surprised: we don't fill in the structured benefit rows on Open Dental's insurance plan (benefits arrive as appointment-note text and the verification date), we don't add dependents' or additional insurance plans, we don't create or update Open Dental recalls, we don't write medical conditions to the problems list (they're in the intake PDF, filed to your Medical History folder or the closest matching folder you have), we don't write medications that aren't on your Open Dental medication list, we don't write no-shows, and we don't create claims inside Open Dental. Claim drafting runs on our side, not inside Open Dental, and drafts are for your staff to review. It is not yet switched on at any Open Dental office we connect to today. Two Open Dental limits shape how all of this runs: the Remote API allows about one request per second per office key, and each list call returns roughly 100 rows at a time. So the biggest pulls (patient walks, insurance, claim history, image backfill) run overnight, and the server running your eConnector needs to stay on after hours, not just during clinic time.
Through Open Dental's Remote API. Our requests go to Open Dental's API service, and Open Dental routes them to the eConnector on your own server, which answers from your database. We hold no database login, install nothing on your server or workstations, and you don't need a VPN or port forwarding. If you're on Open Dental Cloud, talk to us first. We haven't connected a Cloud office yet, and Open Dental may need to enable the Remote API for you.
The Remote API. Open Dental's API authorization scheme is named ODFHIR, which confuses people, but every call we make goes to the regular REST resources (patients, appointments, procedure logs, documents and so on). Open Dental describes its FHIR API as a different API, aimed at interfacing with medical systems, and we don't use it.
Yes. The eConnector is what actually answers the API. If it stops, nothing syncs and nothing writes back until it's running again. The dashboard shows when your eConnector last responded and tells you whether the problem is the eConnector being down, the key being disabled, or the key not being assigned yet. Leave that server on overnight, because the nightly pulls run then.
It's real-time sync for everything we write: a booking, confirmation, payment, filed fax or approved note goes into Open Dental when it happens, and before the AI receptionist or online scheduling books a slot it re-checks Open Dental live. Changes your team makes inside Open Dental reach our side within about 15 minutes, and insurance, claim history, recalls, adjustments and images refresh on nightly and periodic jobs. One quirk worth knowing: when an appointment is deleted in Open Dental, including when staff rebook by making a new appointment and deleting the old one, the API doesn't report the deletion. Our copy can keep showing it as scheduled, and an automated reminder can still go out for it. Breaking the appointment instead of deleting it avoids this, because a status change does sync.
Yes. Open Dental allows roughly one request per second per office key, and list calls come back around 100 rows at a time no matter how many you ask for. We page through results, pace our requests and schedule the largest pulls overnight. In practice that means day-to-day work like booking, confirming and filing a note is quick, while a full pass over a big patient list or an imaging backfill takes hours and runs while you're closed.
It writes appointments (book, cancel as Broken, reschedule), confirmations, patient payments to the ledger, ERA insurance payments to the claim procedure, adjustments for membership discounts (when your API permissions allow adjustments) and cancellation fees, accepted treatment kept in sync with the Active Treatment Plan, procedure notes for AI clinical notes, perio exams, AI charting procedures, documents and filed faxes into Imaging, commlog entries, the insurance Date Last Verified, a benefits summary in the appointment note, and a verified plan when the policyholder has no insurance on file. From intake forms it creates a new chart when none matches, updates address, phone and email on an existing chart, and adds allergies and medications that match your Open Dental lists. Confirmations, cancellations from our side and kiosk check-ins currently replace the whole appointment Note field, so tell us first if your office keeps important text there. It does not write structured benefit rows on the insurance plan, dependents' or additional plans, recalls, no-shows, medical conditions to the problems list, or claims inside Open Dental.
Yes. Card, text-to-pay, checkout, statement and membership payments go in through POST /payments under your Credit Card pay type, and insurance payments from ERAs go onto the claim procedure with a read-back to confirm. A reference on each payment prevents double posting. If a payment can't post, or your Open Dental API permissions don't allow a membership discount adjustment, your office is emailed exactly what to enter.
No, not today. We don't offer a read-only mode. The same key is used for reading and for the writes listed above, because most of the features exist to put something back into your chart. If that's a dealbreaker for your office, tell us before you connect.
You do. In Open Dental, go to Setup > Advanced Setup > API and disable the key, and every call from us stops. You can also disconnect from our dashboard. When your Intake.Dental subscription ends, we switch the connection off on our side and stop calling your Open Dental.
No. We use the API Open Dental publishes for third-party developers, with a standard developer key and a customer key for your office. Intake.Dental is independent and is not affiliated with, certified by, or endorsed by Open Dental Software.
If you run Open Dental, connecting is a key we issue, one checkbox and a paste in Setup > Advanced Setup > API, and about five minutes. After that you get real-time sync: appointments, confirmations, payments, insurance payments, treatment plans, notes, perio, procedures, intake charts, documents, faxes, commlogs and verification results are written back into your chart as they happen, and we stay out of the places we've told you we don't write. Two things to plan for: confirmations and cancellations currently overwrite the appointment note, and the eConnector server needs to stay on overnight. The off switch is inside Open Dental.
Open Dental is a trademark of Open Dental Software, Inc. Intake.Dental is an independent product and is not affiliated with, certified by, endorsed by, or sponsored by Open Dental Software, Inc.
Every Intake.Dental feature for Open Dental is driven through one connection: Open Dental's Remote API, routed through Open Dental's own servers to the eConnector already running in your office. (X-ray files are the one exception: at our request, your Open Dental sends each file out to us over a secure file transfer.) We don't install anything, we don't ask for database credentials, and you don't open a port or set up a VPN. This page covers how setup works, how real-time sync works, what we write into your chart, and what we deliberately don't.
20 minūšu demonstrācija, izmantojot Jūsu grafiku un Jūsu procedūru kodus. Bez pārslēgšanās, bez migrācijas, bez pilnīgas nomaiņas.