Integrations: connected through NexHealth
Automated insurance verification for Dentrix Enterprise
Ardent works alongside Dentrix Enterprise through the NexHealth Synchronizer. It reads upcoming appointments and each patient’s insurance on file, verifies benefits with the payer, portal first and a phone call for what is left open, then fills your practice’s own breakdown sheet and files the PDF into the patient’s documents before the visit, one location at a time.
- Connected through the NexHealth Synchronizer on your Dentrix Enterprise server. It is not a direct Dentrix Enterprise integration.
- Each location is its own practice in Ardent, with its own sheet, timezone and 7:00 AM email recipients.
- Files the finished sheet as a PDF in the patient’s documents, and leaves a one-line note on the appointment when something on file needs fixing.
- Never writes into coverage tables. It runs unattended: the schedule is polled hourly, a 6:00 AM weekday run up to two weeks ahead (five business days by default).
How it works
How does Ardent work with Dentrix Enterprise?
NexHealth’s Synchronizer reads the Dentrix Enterprise schedule and the insurance record on each patient. For each visit inside the window, Ardent checks the payer: the provider portal first, or EDI 270/271 or a faxback where that is the payer’s channel, then an AI phone call for required blanks still open. It draws the answers onto your sheet and files the PDF through NexHealth into the patient’s documents.
What Ardent reads from Dentrix Enterprise
- Upcoming appointments for the location: time, provider, operatory, confirmed / cancelled / no-show flags, and the appointment note.
- The patient: name, date of birth, patient ID.
- The insurance coverage on file: carrier and plan, subscriber ID, relationship to the subscriber, effective and expiration dates, group number, employer, and the payer ID Ardent uses to pick the payer’s playbook.
- Chart history where Dentrix Enterprise exposes it, used to answer the office’s own questions, never a payer’s.
What Ardent writes back to Dentrix Enterprise
| Artifact | Written? | Where and when |
|---|---|---|
| Chart document (PDF) | Yes | The patient’s documents, under the document type your organization chooses. Named insurance-eligibility-<first>-<last>.pdf; filed once per appointment after a successful check inside the window. |
| Appointment note | Yes | One line, [Ardent Dental] <reason>., added under your own note text only when a check could not run for a reason the office can fix. A rewrite replaces only Ardent’s own previous line. |
| Coverage-table fields | No | Never. Plan entry in Dentrix Enterprise stays with your team, done from the filled sheet in the chart. |
Swipe to see the whole table →
The PDF holds the completed sheet page or pages, then the payer’s own documents the portal preserved, any received fax, and the portal screenshots Ardent kept, tiled to letter pages. The REP blank reads Ardent on an unattended upload; the date is the day the check finished.
Setup
How the connection works
Dentrix Enterprise is listed by NexHealth as a server-based system, so the NexHealth Synchronizer is installed on the Dentrix Enterprise server with an admin account; NexHealth’s integrations team can do that remotely. NexHealth then grants Ardent access to each location’s schedule, patients and insurance records. Ardent itself never signs into Dentrix Enterprise, and each location becomes its own practice in Ardent.
- Connect. The Synchronizer goes on the Dentrix Enterprise server. NexHealth’s statement on cost: "Practices don’t pay for the Synchronizer. There’s no setup fee, no subscription." (nexhealth.com; confirm current terms with NexHealth.)
- One practice per location. Each location gets its own connection, display name, timezone, sheet and digest recipients. The 7:00 AM email for a location is addressed to that location.
- Baseline. Ardent pulls every future appointment once per location and checks counts, dates, patient matching, coverage data and payer mapping with your team.
- Switch on, one flag at a time. Hourly polling, then the 6:00 AM ahead-of-visit run, then the 7:00 AM digest, then automatic filing, each after a supervised first run, per location. Automatic filing stays off until a test PDF has reached the intended chart and document category.
We do not promise a go-live date; none is documented for server installs.
One patient, next week
The sheet, filled.
Filed into Dentrix Enterprise as a chart document. Sample data, fictional patient. Watch the full sheet fill in on the home page →
Built-in eligibility
Your current eligibility check and Ardent
Whatever eligibility tool your organization runs today answers the first question, which is whether the patient is covered. Ardent answers the sheet: maximum and remaining, deductible, percentages by category, frequencies and payer-stated history, waiting periods, the prior-extraction question, downgrades and alternate codes. It phones the payer for what the portal or 271 does not state, keeps the source behind every value, and never edits what another tool writes into Dentrix Enterprise.
The exceptions
What still needs a person
Anything Ardent could not verify. Every weekday at 7:00 AM each location’s front desk gets one email, with the subject [Ardent Dental] <Office> Insurance Eligibility for <Weekday, Month D>. It lists each appointment Ardent could not verify and why, in plain words: a member ID missing, a plan that ended, a payer Ardent cannot check yet. On Dentrix Enterprise the same reason also sits in the appointment note.
A required blank the payer would not state stays blank on the sheet, the appointment is flagged "Someone has to call," and it is in that morning’s email. When every appointment verified, the email says so in one line.
Answers
Dentrix Enterprise insurance verification FAQ
No. Ardent files the completed sheet as a PDF in the patient’s documents and, when something on file needs fixing, adds one line to the appointment note. It never edits insurance plans, coverage tables or fee schedules in Dentrix Enterprise. Plan entry in the software stays with your team.
In the patient’s documents, under the document type your organization sets on the connection. The file is named insurance-eligibility-<first>-<last>.pdf, shows REP "Ardent" and the date the check finished, and is filed once per appointment; a chart keeps every filed check. Before automatic filing is switched on, a test PDF is filed by hand and checked in the right chart.
Ardent does not sign into Dentrix Enterprise, so there is no Ardent user in it. NexHealth’s Synchronizer is installed on the server with an admin account, which NexHealth’s team can do remotely, and NexHealth grants Ardent access to each location’s data. Ardent users are your own staff, limited to email addresses on your organization’s domain.
One practice per location. Each has its own connection, timezone, breakdown sheet and 7:00 AM email recipients, and its own hourly polling and 6:00 AM run. A location can use the shared general worksheet or its own sheet, measured once. Access is limited to staff whose email domain maps to the practice.
Your own note text, a blank line, then exactly one line such as [Ardent Dental] Delta Dental of California could not match the patient to the insurance details on file. It is written only for failures the office can fix, and a later rewrite replaces only Ardent’s own line, so what you typed stays untouched. A successful check gets the PDF, not a note.
No. Ardent connects through the NexHealth Synchronizer, which NexHealth lists as supporting Dentrix Enterprise as a server-based system. NexHealth does the reading and the document filing; Ardent does the verification and fills the sheet. The only PMS Ardent connects to directly is CareStack.
The appointment is set to "Needs info" instead of guessed at, the reason goes on the appointment note in Dentrix Enterprise and into that location’s 7:00 AM email, and the app shows a "Fix & re-run" button. Once the front desk corrects the record, the next check runs from the corrected details.