Skip to content
Book a demo
Menu

Integrations

Dentrix analytics, read-only: Calibic for Dentrix

Dentrix analytics with no write path: Calibic reads the Dentrix database over ODBC and lists each table it reads, what it never reads, what Dentrix omits.

4 min readUpdated 2026-10-13

Share
A practice workstation running Dentrix on a generic monitor, no logos visible

Dentrix gives Calibic the widest set of screens of the three systems: production, treatment, recall, claims, patient lists, the schedule and aging. It also has the one gap owners ask about most. Dentrix does not record who edited a payment. This page lists exactly what is read, what is never read, and what Dentrix cannot tell anyone.

How does Calibic connect?

Dentrix desktop stores its data in a FairCom c-tree database, reached over ODBC with the Dentrix ODBC driver. The server accepts SSL connections only, and the driver is 32-bit, which is why the Calibic agent is 32-bit. The agent is a small Windows service on the Dentrix server. It finds the database connection on its own from the Dentrix installation; there is nothing to type.

Dentrix offers no read-only session mode and no way to install change tracking. Read-only therefore rests on two things: the ODBC connection is opened in read-only access mode, and the connector code has no write path at all. Changes are detected by reading Dentrix’s own appointment history table and by comparing snapshots of the payment, adjustment and procedure views. A change made and undone between two reads is not visible, and the Coverage page says so.

Outbound HTTPS only. Nothing listens from outside.

What exactly is read?

Dentrix tables and views What you get in Calibic
admin.v_appointment, admin.appthist, admin.v_appt_book_events, admin.v_appointment_types Daily Huddle, Front Desk, schedule, appointment checks. History carries a user id (which may be blank), a date and a time
admin.v_proclog, admin.fullproclog, admin.proccode, admin.txcase Production, Treatment, case acceptance, Revenue Recovery
admin.payment_view, admin.inspayment_view, admin.adjustment_view, with admin.v_payment_types and admin.v_adjustment_types for the names Collections, End of Day, AR aging. Type names come from your own Dentrix definitions
admin.claim, admin.v_claim_summary, admin.inscarrier, admin.v_maximums, admin.v_patient_insurance, admin.aging Insurance and claims, benefits left, claims aging
admin.v_patient_recall, admin.recallpending Smart Recall, reactivation
admin.v_patient, admin.v_guarantor_balance, admin.v_patientalerts Client Finder, Segments, balances, patient card alerts
admin.referral, admin.refacts, admin.provider_view, admin.operatory_view Referral sources, Scorecards, chairs
admin.rsc (user roster, names only) Names on appointment changes
admin.clinicalnote (dates and lifecycle, never the text) Revenue Integrity

Reads are explicit column lists, never a whole row, because a full-row read on a history table is slow and the server is also running your practice.

What is never touched?

Nothing is written. The admin.rsc table carries a password column; it is never selected. Social Security numbers, licence numbers, street address lines and the text of clinical notes are never read. The patient table has 82 columns and Calibic reads twelve.

Where is Dentrix strong, and where is it limited?

Strong: the breadth above. Almost every Calibic screen is LIVE on Dentrix.

Limited, and why: Dentrix stores no user on payment, procedure or patient edits, so Protect flags the change, not the person. Many edits carry a date but no time of day, which switches off the after-hours rules for those events. There are no sign-in or permission tables, so those checks cannot run. The readable *_audit tables are insurance-import specific; Dentrix writes an internal audit with before and after values, but it is not exposed as a readable table. All of this is stated per check on the Coverage page, with the wording “detected, not attributable”.

How do I set it up?

  1. Sign up. A Business Associate Agreement is sent with every sign up. Calibic is built for HIPAA and does not claim a certification.
  2. Run the installer once, as an administrator, on the Dentrix server. It finds the database connection from the Dentrix installation and checks that the database opens before it finishes.
  3. First numbers appear within minutes. History loads newest first, in small steps with pauses; when the server is busy, the agent slows itself.
  4. Check the source badge (“Dentrix, synced 3 min ago”) and the Coverage page.

Change checks run every 10 to 60 seconds. If the agent is silent for 45 minutes during office hours, you get an email.

Status

LIVE on Dentrix desktop. Not Dentrix Ascend. No claim is made that Henry Schein One endorses or has reviewed this connection; Calibic reads the database your practice owns, with your authorisation.

Next step

If you run Dentrix’s own reports today, start with the guides and see where Calibic adds something: recall report, unscheduled treatment report, audit trail, aging report and the reports overview. Revenue Recovery is the screen most Dentrix offices open first. The Open Dental integration page explains what a system with a real audit log can do that Dentrix cannot.

Useful? Send it to the person who runs your front desk.

Share this page

Questions people ask

Will it name the person who changed a payment?

No, because Dentrix does not record it. Payment, adjustment and procedure edits carry no user in the readable tables. Calibic tells you what changed and when, and marks those checks as detected but not attributable.

Does it work with Dentrix Ascend?

Not today. Ascend is cloud software with no database on your server to read. Dentrix desktop, the G series, is what Calibic connects to.

Keep reading

See it on your own data

Read-only toward Open Dental, Dentrix and Eaglesoft. A Business Associate Agreement is sent with every sign up.