Most analytics tools skip Eaglesoft, or quietly show numbers they have not checked. Calibic connects to it, and takes the other approach: every figure on screen is one whose ledger code has been proven on a live Eaglesoft install, and anything not yet proven shows a dash. This page lists what is read, what is never read, and which screens still carry a BETA label because of that rule.
How does Calibic connect?
Eaglesoft stores its data in a Sybase SQL Anywhere database. The Calibic agent, a small Windows service on the Eaglesoft server, connects over ODBC with the SQL Anywhere driver, usually through the DSN Eaglesoft itself creates. The driver is 32-bit, so the agent is too. The agent finds the database connection from the Eaglesoft installation on that server; nothing is typed in by hand.
The connection is opened in ODBC read-only access mode and the connector code has no write path. Eaglesoft has no change feed, so changes are found by comparing reads, which takes minutes rather than seconds. Outbound HTTPS only.
Verified live across installs from Eaglesoft 17 to 25.
What exactly is read?
| Eaglesoft tables | What you get in Calibic | Status |
|---|---|---|
transactions_header, transactions_detail, eod, paytype |
Daily Huddle money, End of Day, monthly series, Reports | BETA. Shown only where the code meaning is proven |
appointment, appointment_provider, chairs, custom_hours, provider |
Schedule, Front Desk, missed-visit trend | BETA. Statuses derived from arrival, in-chair and walkout times |
planned_services, treatment_plans, treatment_plan_items, services, service_types |
Treatment, unscheduled treatment, Revenue Recovery | BETA |
insurance_claim, insurance, insurance_company, employer |
Claims aging | BETA. Benefits left is off |
patient_recalls, recalls |
Smart Recall, reactivation | BETA |
patient (name, birth date, contact, responsible party) |
Client Finder, Segments | LIVE for the fields listed |
referred_by, other_referral |
Referral sources | Sparse; new patients are “charts created” |
appointment_audit, patient_audit, transactions_header_audit |
Optional change feed for Protect | Only where pe_audit_preference.audit_on is set |
A note on the ledger, because it is where most tools go wrong. In transactions_header, type S is a service, A is a patient payment, P an insurance payment, C a credit adjustment and D a debit adjustment. A void does not delete the row: its status flips to D and Eaglesoft posts a reversing mirror row with status V. Calibic reads the live rows, treats the void as the event, and never counts the mirror. That is why its totals match the end-of-day sheet except on days with voids, and why the difference on those days is exactly the voided entries.
What is never touched?
Nothing is written. Insurance member ids are never read. There is no medical section on the patient card. Clinical note text is never read. Two columns that earlier integrations assumed existed, a chart number and a responsible-party id on the patient table, are not selected because they do not exist on a live install; the real responsible party column is used instead.
Where is Eaglesoft limited, and why?
Ledger rows carry a user_id that points at provider, so Calibic can say which provider an entry is under, not which staff member typed it. The audit tables record modified_by as PES, the system, on every row, so they can say that a row changed and when, never who. Auditing is off by default in Eaglesoft, and Calibic uses those tables only where it is on. Among arrival statuses, only “checked out” is proven, so other status words are derived from the three timestamps. Eaglesoft’s default texting flag is not consent, so texting stays closed for Eaglesoft offices until Calibic holds its own consent record; texting is ROADMAP for everyone in any case.
How do I set it up?
- Sign up. A Business Associate Agreement is sent with every sign up. Calibic is built for HIPAA and does not claim a certification.
- Run the installer once, as an administrator, on the Eaglesoft server. It finds the database connection and checks that the database opens before it finishes.
- First numbers appear within minutes; history follows in small steps.
- Check the source badge (“Eaglesoft, synced 11 min ago”) and the Coverage page, which lists each check as active, limited or not available, with the reason.
Status
The connector is LIVE. Several screens are BETA for the reason above: a figure is withheld until its code is proven.
Next step
If you run Eaglesoft’s own reports today, start with the guides: recall report, the reports that matter, audit trail, the built-in dashboard, remote access and statements. The Front Desk and End of Day page shows the daily close Calibic reads from the ledger above. The Dentrix integration page is the comparison most multi-system groups ask for.