A clinic day, connected

The patient record moves with your team.

Book at reception, open the same record at the chair, then bill the work that was completed. IvoryCRM keeps those handoffs in one place.

16 clinic modulesFDI chartingGST-aware billing
A dentist explaining a treatment model to a patient
At the chairPlan with the patient record open.
Clinical

From registration to completed treatment.

Open the patient once, then move through appointments, charting and treatment without rebuilding the record.

A dentist preparing the chair before an examination
Chair readyClinical context stays close to the work.
01

Registration and search

One record per person, found by name, phone, or identifier, with duplicate awareness and the contact details a desk actually needs.

Patients
02

Appointments

Booked against an operatory, an operator, and a speciality, across branches, without double-booking a chair.

Schedule
03

Live queue

Called, seated, in chair, on hold, finished. The desk sees the position; the clinical detail stays at the chair.

Queue
04

Visits and encounters

An encounter opens when the patient is seated and closes when the work is done, so time in the chair is not a guess.

Visits
05

Tooth charting

An odontogram in FDI notation, with surfaces, and treatments that know whether they belong to a tooth, an arch, or the whole mouth.

Clinical
06

Periodontal charting

Perio readings charted per tooth and per site, so a comparison against last month is a real comparison.

Perio
07

Imaging orders

An image is requested with a reason and a status. “Why was this taken” is the question an audit asks months later.

Imaging
08

Multi-visit treatment courses

Plan stages for treatments such as root canals. Dates for pending stages recalculate from the previous visit’s actual completion.

Treatment
Operational

The clinic keeps moving after the chair is empty.

Prescriptions, lab work, recalls, stock and collections remain attached to the treatment that created them.

09

Prescriptions

Write, dispense and print from a formulary controlled by the clinic.

Rx
10

Lab orders

Work sent out, tracked, and returned against the patient it was made for, not against a tray of paperwork.

Lab
11

Recalls

Who is due for a cleaning, a review, or the second half of a bridge that was never started.

Recalls
12

Billing and GST

Treatment is exempt healthcare; goods and cosmetic work is not. Place of supply, HSN, and the day book follow from that.

Invoices
13

Inventory

Consumables and stock movements against the procedures that actually consume them, with warnings before a chair is interrupted.

Stock
14

Equipment

Keep each machine and its maintenance history together for the branch that uses it.

Equipment
15

Claims and payouts

Insurance claims and practitioner payouts reconciled against the work that justified them.

Claims
16

Reports and analytics

See chair use, production and collections by branch or speciality.

Reports

Patient data

Each clinic’s records stay inside that clinic.

The database enforces this boundary on every request. The application cannot bypass it, and the test suite checks every route against another clinic’s data.

isolation and infrastructure tests

  1. One clinic cannot read another. Forced row-level security on every tenant table: a query that forgets its tenant filter returns zero rows.
  2. The app role cannot escalate. No DDL, no BYPASSRLS. Startup fails loudly if that ever changes.
  3. Tenant context is per transaction. Set with is_local, so a pooled connection cannot carry one clinic’s tenant into the next request.
  4. Every route is probed in CI. A cross-tenant probe over each registered route. No probe, no merge.
Tenancy

One chain’s patients can never appear in another’s.

This is the failure that would end the product, so it is not left to developer discipline. It is enforced in the database, verified automatically, and stated here in full rather than reduced to a badge.

Talk through your rollout
  1. Isolation is a database setting, not a convention.

    Every tenant table has row-level security enabled and forced. A query that forgets its tenant filter returns zero rows — not another chain’s patients.

  2. The application cannot bypass it.

    The app connects as a role that holds no DDL and no BYPASSRLS, and refuses to start if its database role can ever bypass the policy.

  3. Tenant context is per transaction.

    Set with is_local inside the request transaction, so a pooled connection cannot carry one clinic’s tenant into the next request.

  4. Fields are allowlisted, not nulled.

    Every response is projected through an explicit allowlist. Lacking permission on a field leaves the key absent from the JSON.

  5. An unguarded route fails the build.

    CI runs a cross-tenant probe across every registered route. A new route without a probe does not merge.

The record itself

Handling data you are trusted with.

Control who can open a record, handle its documents and export its data.

  1. Reads are audited, not just writes.

    For a medical record, who looked matters as much as who changed it. The audit log is a first-class view, not a database table nobody opens.

  2. Documents are scoped to their owner.

    Files and signed media links resolve against the patient and organisation that own them, so a shared link does not outlive its permission.

  3. Export is a permission, not a support ticket.

    A DPDP data export is its own capability on the permission catalog, so a subject access request is a workflow rather than an incident.

  4. A route that declares nothing is closed.

    Permissions compile from a catalog, so a new endpoint with no declared permission is a build failure rather than a loophole someone finds later.

See the whole day, not another dashboard.

Start with the workflows your team touches every day.

See pricing